Method and apparatus for avoiding network re-synchronization in stationary M2M devices

ABSTRACT

Techniques for determining if it is safe for a mobile device to transition directly from a traffic session to a paging mode and for avoiding network re-synchronization procedures in stationary M2M devices are disclosed. It may be safe for direct transition if before-call and in-call network parameters correspond. If safe, the mobile device may transition from the traffic session directly to the paging mode to begin immediately monitoring the paging channel. In stationary M2M devices, paging information is stored before the traffic session and, once the traffic session is complete, the M2M device may be configured to receive paging messaging based on the stored paging information. The M2M device may also store system access information and confirm the validity of the information before returning to the sleep state. The stationary M2M device avoids network re-synchronization procedures. Other aspects, embodiments, and features are also claimed and described.

PRIORITY CLAIM

This application claims priority to and the benefit of U.S. ProvisionalApplication No. 61/799,475, filed 15 Mar. 2013, which is incorporated byreference herein as if fully set forth below and for all applicablepurposes.

TECHNICAL FIELD & BACKGROUND

The technology discussed below relates generally to wirelesscommunication, and more specifically to methods, systems, and devicesconfigured for fast transition from a traffic session to a paging modeand also to avoid network re-synchronization procedures for stationaryMachine-to-Machine (M2M) devices.

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing the available system resources (e.g., time, frequency, andpower).

One or more communication devices (e.g., a user equipment,Machine-to-Machine (M2M) device, mobile station, a tablet device, alaptop, etc.) may be operable on the wireless communications system tocommunicate with one another, or other entities through the wirelesscommunications system. Generally, the communications device registerswith a base station of the wireless communications system and thenenters into a paging or sleep mode where it monitors a Paging Channel(PCH). When the communications device needs to communicate over thewireless communications system (e.g., to initiate or receive a voicecall, transmit or receive data, etc.), the device will transition fromthe paging mode to an active mode where it enters into a traffic sessionand communicates via a Traffic Channel (TCH) on the wirelesscommunications system.

When the communications device completes the traffic session, the devicewill generally transition back to the paging mode where it monitors thePCH. To transition from the traffic session back to the paging mode, thecommunications device will generally complete a re-synchronizationprocess that involves pilot acquisition and SYNC message decoding. Thepilot acquisition and SYNC message decoding process involves receivingand decoding messages from the base station, which takes time for thecommunications device to complete. During this re-synchronization time,the communications device cannot monitor the PCH and may, for example,miss an incoming paging signal indicating an incoming call for thecommunications device. Furthermore, the pilot acquisition and SYNCmessage decoding process utilizes the hardware components on thecommunication device to receive, decode, store, etc., there-synchronization messages. Operating the hardware on thecommunications device reduces power efficiency of the device.

SUMMARY

The described features generally relate to one or more improved systems,methods, and/or apparatuses for avoiding network re-synchronizationprocedures by transitioning directly from a traffic session to a pagingmode in a stationary M2M device. The described techniques may be usedby, for example, a M2M device to configure, upon termination of atraffic session, the M2M device to receive paging messaging from a basestation according to stored paging information. In accordance withcertain aspects, the M2M device may store paging information beforeinitiation of a traffic session and, upon termination of the trafficsession, configure the M2M device to receive paging messaging accordingto the stored paging information. According to other aspects, the M2Mdevice stores system access information (e.g., system overheadinformation) and configures the M2M device for receiving the pagingmessaging if the system access information has not expired. The systemaccess information may expire if an associated overhead timer hascompleted its cycle. If the system access information has expired (e.g.,the overhead timer has completed its cycle), aspects provide forvalidating and, if necessary, updating the system access informationbefore configuring the M2M device to transition to the paging mode toreceive paging messaging.

In accordance with certain embodiments, a method of wirelesscommunication performed by a stationary machine-to-machine (M2M) deviceis provided. The method may include storing, before initiation of atraffic session with a base station of a wireless communicationsnetwork, paging information associated with the base station. The methodmay also include configuring, upon termination of the traffic session,the M2M device for receiving paging messaging from the base stationaccording to the stored paging information. The paging information mayinclude a paging channel rate, and where the method includes decodingpaging signaling transmitted by the base station utilizing the pagingchannel rate. The paging information may include a paging slot cycle,and where the method includes decoding paging signaling transmitted bythe base station utilizing the paging slot cycle. The paging informationmay include parameters for decoding a quick paging channel, and wherethe method includes decoding paging signaling transmitted by the basestation over the quick paging channel utilizing the stored paginginformation. Configuring the M2M device for receiving paging messagingfrom the base station may include configuring the M2M device forreceiving paging messaging from the base station without performing oneor more of pilot acquisition or synchronization signal decoding.

Some aspects may provide for the method to include receiving, beforeinitiation of the traffic session, system access information associatedwith the base station. The system access information may be transmittedby the base station in a plurality of access configuration messages. Themethod may include storing the received system access information anddetermining, upon termination of the traffic session, that the storedsystem access information remains valid. The method may includetransitioning directly to a sleep state based on the determining thatthe stored system access information remains valid. The method mayinclude disabling reception for one or more of the plurality of accessconfiguration messages based on the determination that the stored systemaccess information remains valid. The access configuration messages mayinclude one or more of a system parameter message, an access parametermessage, a neighbor list message, or a channel list message. Determiningthat the stored system access information remains valid may be based onan overhead timer associated with the stored system access information.

According to certain aspects, the method includes receiving, beforeinitiation of the traffic session, system access information associatedwith the base station, the system access information transmitted by thebase station in a plurality of access configuration messages. The methodmay store the received system access information and determine, upontermination of the traffic session, that the stored system accessinformation has expired. If expired, the method may validate the storedsystem access information prior to transitioning to a sleep state.Validating the stored system access information may include receivingone of the plurality of access configuration messages and comparing aconfiguration sequence number associated with the stored system accessinformation to a configuration sequence number associated with thereceived one of the plurality of access configuration messages.

According to other embodiments, the method may include disablingreception of one or more of the plurality of access configurationmessages based on determining that the configuration sequence numberassociated with the stored system access information and theconfiguration sequence number associated with the received one of theplurality of access configuration messages are a same configurationsequence number. The method may include enabling reception of theplurality of access configuration messages based on determining that theconfiguration sequence number associated with the stored system accessinformation is different from the configuration sequence numberassociated with the received one of the plurality of accessconfiguration messages. The method may include receiving, during thetraffic session, timing information for synchronization with the basestation where configuring the M2M device to receive paging messagingtransmitted by the base station is based at least in part on the timinginformation.

According to other embodiments, a wireless communications systemconfigured to avoid network re-synchronization procedures by astationary machine-to-machine (M2M) device is provided. The system caninclude means for storing, before initiation of a traffic session with abase station of a wireless communications network, paging informationassociated with the base station; and means for configuring, upontermination of the traffic session, the M2M device for receiving pagingmessaging from the base station according to the stored paginginformation. The system can also include means for receiving, beforeinitiation of the traffic session, system access information associatedwith the base station, the system access information transmitted by thebase station in a plurality of access configuration messages; means forstoring the received system access information; means for determining,upon termination of the traffic session, that the stored system accessinformation remains valid; and means for transitioning directly to asleep state based on the determining that the stored system accessinformation remains valid.

According to certain aspects, the means for transitioning directly tothe sleep state further includes means for disabling reception for oneor more of the plurality of access configuration messages based on thedetermination that the stored system access information remains valid.The determining that the stored system access information remains validcan be based on an overhead timer associated with the stored systemaccess information. The system can also include means for receiving,before initiation of the traffic session, system access informationassociated with the base station, the system access informationtransmitted by the base station in a plurality of access configurationmessages; means for storing the received system access information;means for determining, upon termination of the traffic session, that thestored system access information has expired; and means for validatingthe stored system access information prior to transitioning to a sleepstate. The means for validating the stored system access information caninclude means for receiving one of the plurality of access configurationmessages; and means for comparing a configuration sequence numberassociated with the stored system access information to a configurationsequence number associated with the received one of the plurality ofaccess configuration messages.

According to some aspects, the system also includes means for disablingreception of one or more of the plurality of access configurationmessages based on determining that the configuration sequence numberassociated with the stored system access information and theconfiguration sequence number associated with the received one of theplurality of access configuration messages are a same configurationsequence number. The system can include means for enabling reception ofthe plurality of access configuration messages based on determining thatthe configuration sequence number associated with the stored systemaccess information is different from the configuration sequence numberassociated with the received one of the plurality of accessconfiguration messages. The plurality of access configuration messagescan include one or more of a system parameter message, an accessparameter message, a neighbor list message, or a channel list message.

The means for configuring the M2M device for receiving paging messagingfrom the base station can include means for configuring the M2M devicefor receiving paging messaging from the base station without performingone or more of pilot acquisition or synchronization signal decoding.When the stored paging information includes a paging channel rate, thesystem can further include means for decoding paging signalingtransmitted by the base station utilizing the paging channel rate. Whenthe stored paging information includes a paging slot cycle, the systemcan further include means for decoding paging signaling transmitted bythe base station utilizing the paging slot cycle. When the stored paginginformation includes parameters for decoding a quick paging channel, andthe system can further includes means for decoding paging signalingtransmitted by the base station over the quick paging channel utilizingthe stored paging information. According to some aspects, the system caninclude means for receiving, during the traffic session, timinginformation for synchronization with the base station. Accordingly, thesystem can include means for configuring the M2M device to receivepaging messaging transmitted by the base station is based at least inpart on the timing information.

According to other embodiments, a computer program product for wirelesscommunication by a stationary machine-to-machine (M2M) device isprovided. The program can include a non-transitory computer readablemedium that includes code for storing, before initiation of a trafficsession with a base station of a wireless communications network, paginginformation associated with the base station; and code for configuring,upon termination of the traffic session, the M2M device for receivingpaging messaging from the base station according to the stored paginginformation. The program can also include code for receiving, beforeinitiation of the traffic session, system access information associatedwith the base station, the system access information transmitted by thebase station in a plurality of access configuration messages; code forstoring the received system access information; code for determining,upon termination of the traffic session, that the stored system accessinformation remains valid; and code for transitioning directly to asleep state based on the determining that the stored system accessinformation remains valid.

According to other aspects, the code for transitioning directly to thesleep state further includes code for disabling reception for one ormore of the plurality of access configuration messages based on thedetermination that the stored system access information remains valid.The code for determining that the stored system access informationremains valid can be based on an overhead timer associated with thestored system access information. The program can include code forreceiving, before initiation of the traffic session, system accessinformation associated with the base station, the system accessinformation transmitted by the base station in a plurality of accessconfiguration messages; code for storing the received system accessinformation; code for determining, upon termination of the trafficsession, that the stored system access information has expired; and codefor validating the stored system access information prior totransitioning to a sleep state.

The code for validating the stored system access information can furtherinclude code for receiving one of the plurality of access configurationmessages; and code for comparing a configuration sequence numberassociated with the stored system access information to a configurationsequence number associated with the received one of the plurality ofaccess configuration messages. The program can also include code fordisabling reception of one or more of the plurality of accessconfiguration messages based on determining that the configurationsequence number associated with the stored system access information andthe configuration sequence number associated with the received one ofthe plurality of access configuration messages are a same configurationsequence number.

According to certain aspects, the program can also include code forenabling reception of the plurality of access configuration messagesbased on determining that the configuration sequence number associatedwith the stored system access information is different from theconfiguration sequence number associated with the received one of theplurality of access configuration messages. The plurality of accessconfiguration messages can include one or more of a system parametermessage, an access parameter message, a neighbor list message, or achannel list message. The code for configuring the M2M device forreceiving paging messaging from the base station can also include codefor configuring the M2M device for receiving paging messaging from thebase station without performing one or more of pilot acquisition orsynchronization signal decoding. When the stored paging informationincludes a paging channel rate, the program further includes code fordecoding paging signaling transmitted by the base station utilizing thepaging channel rate.

According to other aspects, when the stored paging information includesa paging slot cycle, the program also includes code for decoding pagingsignaling transmitted by the base station utilizing the paging slotcycle. When the stored paging information includes parameters fordecoding a quick paging channel, the program can include code fordecoding paging signaling transmitted by the base station over the quickpaging channel utilizing the stored paging information. The program canalso include code for receiving, during the traffic session, timinginformation for synchronization with the base station. Accordingly, thecode for configuring the M2M device to receive paging messagingtransmitted by the base station can be based at least in part on thetiming information.

According to even further embodiments, a stationary machine-to-machine(M2M) device configured to avoid network re-synchronization is provided.The device can include at least one controller. The controller can beconfigured to store, before initiation of a traffic session with a basestation of a wireless communications network, paging informationassociated with the base station; and configure, upon termination of thetraffic session, the M2M device for receiving paging messaging from thebase station according to the stored paging information. The controllercan also be configured to receive, before initiation of the trafficsession, system access information associated with the base station, thesystem access information transmitted by the base station in a pluralityof access configuration messages; store the received system accessinformation; determine, upon termination of the traffic session, thatthe stored system access information remains valid; and transitiondirectly to a sleep state based on the determining that the storedsystem access information remains valid. The controller can be furtherconfigured to disable reception for one or more of the plurality ofaccess configuration messages based on the determination that the storedsystem access information remains valid.

According to certain aspects, determining that the stored system accessinformation remains valid is based on an overhead timer associated withthe stored system access information. The controller can further beconfigured to receive, before initiation of the traffic session, systemaccess information associated with the base station, the system accessinformation transmitted by the base station in a plurality of accessconfiguration messages; store the received system access information;determine, upon termination of the traffic session, that the storedsystem access information has expired; and validate the stored systemaccess information prior to transitioning to a sleep state.

According to some aspects, the controller configured to validate thestored system access information is also configured to receive one ofthe plurality of access configuration messages; and compare aconfiguration sequence number associated with the stored system accessinformation to a configuration sequence number associated with thereceived one of the plurality of access configuration messages. Thecontroller can be further configured to disable reception of one or moreof the plurality of access configuration messages based on determiningthat the configuration sequence number associated with the stored systemaccess information and the configuration sequence number associated withthe received one of the plurality of access configuration messages are asame configuration sequence number. The controller can further beconfigured to enable reception of the plurality of access configurationmessages based on determining that the configuration sequence numberassociated with the stored system access information is different fromthe configuration sequence number associated with the received one ofthe plurality of access configuration messages.

According to further aspects, the plurality of access configurationmessages include one or more of a system parameter message, an accessparameter message, a neighbor list message, or a channel list message.The controller being configured to configure the M2M device forreceiving paging messaging from the base station also includes thecontroller being further configured to configure the M2M device forreceiving paging messaging from the base station without performing oneor more of pilot acquisition or synchronization signal decoding. Whenthe stored paging information includes a paging channel rate, thecontroller can be configured to decode paging signaling transmitted bythe base station utilizing the paging channel rate. When the storedpaging information includes a paging slot cycle, the controller can beconfigured to decode paging signaling transmitted by the base stationutilizing the paging slot cycle. When the stored paging informationincludes parameters for decoding a quick paging channel, the controllercan be configured to decode paging signaling transmitted by the basestation over the quick paging channel utilizing the stored paginginformation. According to further aspects, when the controller isconfigured to receive, during the traffic session, timing informationfor synchronization with the base station, the controller is alsoconfigured to configure the M2M device to receive paging messagingtransmitted by the base station based at least in part on the timinginformation.

Further scope of the applicability of the described methods andapparatuses will become apparent from the following detaileddescription, claims, and drawings. The detailed description and specificexamples are given by way of illustration only, since various changesand modifications within the spirit and scope of the description willbecome apparent to those skilled in the art.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the following drawings. In theappended figures, similar components or features may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem;

FIG. 2 is a diagram illustrating an example of a wireless communicationssystem;

FIG. 3 is a diagram illustrating an exemplary communication flow betweena communications device and a base station of the wirelesscommunications system;

FIG. 4 is another diagram illustrating a communication flow between acommunications device and two base stations of the wirelesscommunications system in accordance with a handover procedure;

FIG. 5 is a process diagram illustrating transition from a trafficsession to a paging mode where the paging channel is monitored;

FIG. 6 is another process diagram illustrating, in greater detail, anexemplary hierarchical flow for determining whether it is safe totransition directly from a traffic session to a paging mode;

FIG. 7 is a block diagram showing aspects of an exemplary device for adirect traffic session to paging mode transition;

FIG. 8 is a block diagram showing aspects of yet another exemplarydevice for a direct traffic session to paging mode transition;

FIG. 9 is a block diagram of an example of a communications device;

FIG. 10 is a flowchart of a method for fast traffic session to pagingmode transition;

FIG. 11 is a flowchart of another method for fast traffic session topaging mode transition;

FIG. 12 is a flowchart of yet another method for fast traffic session topaging mode transition;

FIG. 13 is a diagram illustrating an exemplary communication flowbetween a M2M device and a base station;

FIG. 14 is a diagram illustrating another exemplary communication flowbetween a M2M device and a base station;

FIG. 15 is a process diagram illustrating transition from a trafficsession to a paging mode in a M2M device;

FIG. 16 is another process diagram illustrating transition from atraffic session to a paging mode in a M2M device;

FIG. 17 is a block diagram of a device;

FIG. 18 is a block diagram of another device;

FIG. 19 is a block diagram of an example of a M2M device;

FIG. 20 is flowchart of a method to transition from a traffic session toa paging mode in a M2M device;

FIG. 21 is a flowchart on another method to transition from a trafficsession to a paging mode in a M2M device; and

FIG. 22 is a flowchart of yet another method to transition from atraffic session to a paging mode in a M2M device.

DETAILED DESCRIPTION

Methods, systems, and devices are described for fast traffic session topaging mode transition. Once the traffic session is terminated (e.g.,the call is released), a determination is made as to whether it is safefor a direct traffic session to paging mode transition. The directtraffic session to paging mode transition may include transitioningdirectly from communication over a traffic channel for the trafficsession to receiving paging information via a paging channel withoutperforming pilot signal detection and acquisition, sync channelreception and decoding, etc. If it is determined safe, aspects providefor determining parameters for receipt of paging information via thepaging channel. For example, paging channel information may bedetermined for receiving and decoding paging messages via the pagingchannel. Alternatively, a blind detection scheme may be utilized basedon one or more last known good parameters for the paging channel.

In accordance with some aspects, before-call network parameters may bestored before initiation of a traffic session. The before-call networkparameters may be stored while a mobile device is in a paging mode(e.g., an IDLE or sleep mode) and monitoring the paging channel.Alternatively, the before-call network parameters may be stored as apart of the call setup process as the mobile device transitions from thepaging mode to a traffic session where it communicates via the trafficchannel. While in the traffic session, or as a part of the call releaseprocedure, in-call network parameters may be stored. Upon termination ofthe traffic session, the mobile device may determine whether a safetransition directly to the paging mode is permissible based on thebefore-call and in-call network parameters. For example, the mobiledevice may compare the before- and in-call network parameters using ahierarchical flow. The mobile device may determine synchronizationinformation used for a direct transition from the traffic session to thepaging mode.

In some embodiments, the mobile device may have two, independentlytunable receivers. A first receiver may be tuned to communicate via thetraffic channel while in the traffic session while a second receiver maybe tuned to receive paging information via the paging channel while inthe traffic session. The mobile device may receive current paginginformation via the second receiver and may safely transition directlyfrom the traffic session to a paging mode when the traffic sessionterminates.

In accordance with other embodiments, methods, systems, and devices aredescribed for avoiding network re-synchronization procedures forstationary M2M devices. The described features provide for configuringthe M2M device to avoid network re-synchronization procedures andtransition directly to the paging mode once the traffic session hasterminated. The M2M device may store paging information associated witha base station before initiation of a traffic session. Once the trafficsession is terminated, the M2M device may be configured to receivepaging messaging from the base station based on the stored paginginformation. System access information (e.g., network overheadinformation) may also be stored and the M2M device may determine if thestored system access information has expired. In one example, anoverhead timer may be associated with the system access information andinitiated when the system access information is stored. As long as theoverhead timer has not completed its cycle, the system accessinformation may be considered current. If the timer has expired, the M2Mdevice may validate and, if necessary, update the system accessinformation.

In accordance with other aspects, the described features may permit thestationary M2M device to avoid having to receive and decode certainaccess configuration messages when the system access information iscurrent and/or valid. The system access information may be received fromthe base station in one or more access configuration messages. Theaccess configuration messages may include configuration sequence numbersthat may be associated with a set of network parameters for the wirelesscommunications system (e.g., network overhead parameters). Thestationary M2M device may compare the configuration sequence number fromone or more access configuration messages to a configuration sequencenumber associated with system access information currently stored on theM2M device. If the configuration sequence numbers match, the M2M devicemay determine that the stored system access information is valid and maydisable reception of additional access configuration messages.Alternatively, if the configuration sequence numbers do not match, theM2M device may enable reception of one or more subsequent system accessmessages to update the stored system access information.

Techniques described herein may be used for various wirelesscommunications systems such as cellular wireless systems, Peer-to-Peerwireless communications, wireless local access networks (WLANs), ad hocnetworks, satellite communications systems, and other systems. The terms“system” and “network” are often used interchangeably. These wirelesscommunications systems may employ a variety of radio communicationtechnologies for multiple access in a wireless system such as CodeDivision Multiple Access (CDMA), Time Division Multiple Access (TDMA),Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA),Single-Carrier FDMA (SC-FDMA), and/or other technologies. Generally,wireless communications are conducted according to a standardizedimplementation of one or more radio communication technologies called aRadio Access Technology (RAT). A wireless communications system ornetwork that implements a Radio Access Technology may be called a RadioAccess Network (RAN).

Examples of RATs employing CDMA techniques include CDMA2000, UniversalTerrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95,and IS-856 standards. IS-2000 Releases 0 and A are commonly referred toas CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to asCDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. Examples of TDMAsystems include various implementations of Global System for MobileCommunications (GSM). Examples of RATs employing FDMA and/or OFDMAinclude Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA andE-UTRA are part of Universal Mobile Telecommunication System (UMTS).3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releasesof UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM aredescribed in documents from an organization named “3rd GenerationPartnership Project” (3GPP). CDMA2000 and UMB are described in documentsfrom an organization named “3rd Generation Partnership Project 2”(3GPP2). The techniques described herein may be used for the systems andradio technologies mentioned above as well as other systems and radiotechnologies.

Thus, the following description provides examples, and is not limitingof the scope, applicability, or configuration set forth in the claims.Changes may be made in the function and arrangement of elementsdiscussed without departing from the spirit and scope of the disclosure.Various embodiments may omit, substitute, or add various procedures orcomponents as appropriate. For instance, the methods described may beperformed in an order different from that described, and various stepsmay be added, omitted, or combined. Also, features described withrespect to certain embodiments may be combined in other embodiments.

Referring first to FIG. 1, a block diagram illustrates an example of awireless communications system 100. The system 100 includes basestations 105 (or cells), mobile devices 115, a controller 130, and acore network 140 (the controller 130 may be integrated into the corenetwork 140). In one example, the controller 130 may be coupled to a setof base stations 105 and provide coordination and control for these basestations 105. The controller 130 may communicate with the base stations105 via wireless or wireline backhaul. The base stations 105 may alsocommunicate with one another directly or indirectly and/or via wirelessor wireline backhaul. The core network 140 may include network entitiessuch as a Mobile Switching Center (MSC), Serving Gateway, Packet DataServing Node, Packet Data Network Gateway, Mobility Management Entity,Home Location Register (HLR), Visitor Location Register (VLR), etc.

The system 100 may support operation on multiple carriers (waveformsignals of different frequencies). Multi-carrier transmitters maytransmit modulated signals simultaneously on the multiple carriers. Forexample, each modulated signal may be a multi-carrier channel modulatedaccording to the various radio technologies described above. Eachmodulated signal may be sent on a different carrier and may carrycontrol information (e.g., pilot signals, control channels, etc.),overhead information, data, etc. The system 100 may include multipleRANs with overlapping or non-overlapping coverage areas.

The base stations 105 may wirelessly communicate with the mobile devices115 via a base station antenna (not shown). The base stations 105 maycommunicate with the devices 115 under the control of the controller 130via multiple carriers. Each of the base stations 105 may providecommunication coverage for a respective geographic area. In someembodiments, base stations 105 may be referred to as a base transceiverstation (BTS), a radio base station, an access point, a radiotransceiver, a basic service set (BSS), an extended service set (ESS), aNodeB, eNodeB (eNB), Home NodeB, a Home eNodeB, or some other suitableterminology. The controller 130 may be referred to as a Base StationController (BSC), Radio Network Controller (RNC), and/or the like. Thecoverage area for each base station 105 here is identified as 110-a,110-b, or 110-c. The coverage area for a base station may be dividedinto sectors (e.g., 112-b-1, 112-b-2, 112-b-3, etc.). The system 100 mayinclude base stations 105 of different types (e.g., macro, pico, and/orfemto base stations). A macro base station may provide communicationcoverage for a relatively large geographic area (e.g., 35 km in radius).A pico base station may provide coverage for a relatively smallgeographic area (e.g., 2 km in radius), and a femto base station mayprovide communication coverage for a relatively smaller geographic area(e.g., 50 m in radius). There may be overlapping coverage areas fordifferent technologies.

The devices 115 may be dispersed throughout the coverage areas 110. Eachdevice 115 may be stationary or mobile. In one configuration, thedevices 115 may be able to communicate with different types of basestations such as, but not limited to, macro base stations, pico basestations, and femto base stations, via links 125.

Generally, mobile devices 115 monitor one or more pilot signals frombase stations 105 to determine which networks and/or base stations 105may provide the best downlink and/or uplink channel conditions. Themobile devices 115 may then select a RAN and/or particular base station105 for communication, synchronize with the base station, and registeror “camp” on the network. Registration of a device on a network may alsobe called network attachment. Synchronization may involve acquiringsystem reference time from a synchronization channel, and receivingsystem identification and system parameter information. Registrationand/or attachment may include sending an attach request from the deviceto the RAN, which may allocate a device identifier for the registereddevice (e.g., Temporary Mobile Subscriber Identity (TMSI), and thelike). Registration may also include authentication of the device on thenetwork, bearer context setup in the device and network, and/or mobilitymanagement by the network.

Mobility management provides functions associated with trackingregistered devices so the network may locate the subscribers for mobileterminated (MT) communications such as calls, short messaging service(SMS), and/or other services that may require MT communications. Forlocating mobile devices, the network may be divided into networklocation areas. Each network location area may be associated with agroup of base stations 105. Where each base station supports multiplecells or sectors, each network location area may be composed of multiplecells or sectors from multiple base stations.

While “camped” on a particular network or base station, mobile devices115 may monitor network overhead and paging messaging for the networkand update network registration periodically or based on a change todevice or network parameters. Network overhead messaging may includevarious information used for communicating with the particular network.For example, network overhead messaging may include system parameters,access parameters, neighbor lists, channel lists, etc. System parametersmay include, for example, paging channel information, parameters relatedto device registration, and/or parameters to aid pilot acquisition.Access parameters may include, for example, parameters related to theconfiguration of the Access Channel (e.g., preamble size, maximum size,etc.) and/or control parameters used to stabilize the Access Channel.Neighbor lists may include time offset of pilots and basic configurationfor neighboring access points. Channel list parameters may includefrequency assignments for paging, access, and/or traffic channels.Network overhead messaging may be sent on, for example, synchronizationchannels, paging channels (PCHs), common control channels (CCHs), and/orbroadcast control channels (BCCHs) of the network.

Generally, while not actively communicating (e.g., via a voice call,etc.), mobile devices 115 may be in a paging mode where they conservepower and enable reception during short periods of time to receivepaging information. Mobile devices 115 may communicate with the networkin traffic sessions that may be mobile originated (MO) or mobileterminated (MT) traffic sessions. Upon termination of a traffic session,the mobile device 115 will complete a re-synchronization process beforetransitioning back to the paging mode. This re-synchronization processmay involve pilot signal detection and also reception and decoding ofone or more SYNC messages (e.g., over a synchronization channel). Duringthis re-synchronization process, the mobile device 115 cannot monitorthe PCH, and may miss an incoming paging message (e.g., a call setupmessage) from the base station 105. Additionally, the mobile device 115is not able to originate new traffic sessions (e.g., call, SMS, etc.)during the re-synchronization process. The delay time between thetraffic session and receiving paging information may reduce theperceived user experience, especially when users are transmitting and/orreceiving short calls and/or messages.

While the system 100 may be designed primarily for wirelesscommunications involving humans, the system 100 may support M2M devices120 that perform various functions, capture information, and/orcommunicate information with limited or no human intervention. Forexample, M2M devices 120 may include sensors and/or meters formonitoring and/or tracking other devices, environmental conditions, etc.M2M devices 120 may be used with various applications such as, but notlimited to, remote monitoring, measurement and condition recording,fleet management and asset tracking, in-field data collection,distribution, physical access control, and/or storage, etc.

M2M devices 120 may be standalone devices or, in embodiments, M2Mdevices 120 may be modules incorporated in other devices. For example,devices (e.g., user equipment, mobile stations, etc.) such as smartphones, cellular phones and wireless communications devices, personaldigital assistants (PDAs), tablets, other handheld devices, netbooks,ultrabooks, smartbooks, notebook computers, surveillance cameras,handled medical scanning devices, home appliances, etc. may include oneor more M2M device modules 120. In the ensuing description, varioustechniques are described as applied to communications and processing fora system including a network and one or more M2M devices. It should beunderstood that the described techniques may be advantageously appliedto other devices such as those incorporating M2M modules and/or otherwireless communication devices.

The information collected by the M2M devices 120 may be transmittedacross a network that includes components of system 100 to a back-endsystem, such as a server. The transmission of data to/from the M2Mdevices 120 may be routed through the base stations 105. The basestations 105 may communicate with the M2M devices 120 on a forward linkfor transmitting signaling and/or information to the M2M devices 120 anda reverse link for receiving signaling and/or information from the M2Mdevices 120.

Various aspects of M2M devices 120 may pose different challenges forwireless communications networks than traditional wireless communicationinvolving humans. For instance, M2M devices 120 may have aspects thatdiffer from traditional wireless devices with regard to mobility andpower efficiency. For example, certain M2M devices 120 may bepermanently installed in a static location or have periods of time wheretheir locations may be static, followed by periods of time of mobility.In addition, certain M2M devices 120 may need to be power efficient. Forexample, some M2M devices may not have a readily accessible power sourceand extended battery life may be important to reduce required serviceand maintenance.

In certain embodiments, the system 100 is configured for fast trafficsession to paging mode transition in the mobile devices 115 and/or M2Mdevices 120. The described techniques may be used, for example, bymobile devices 115 to transition directly from the traffic session to apaging mode (e.g., IDLE or SLEEP state, etc) where the PCH is monitored.Generally, the techniques may determine whether it is safe to performdirect traffic session (e.g., using TCH) to paging mode (e.g.,monitoring PCH) transition after a call has ended based on comparingcertain network parameters stored prior to the call (e.g., before-callnetwork parameters) with network parameters obtained during the call(e.g., during the traffic session while on the TCH). Upon termination ofthe call, the network parameters are compared and it may be determinedwhether it is safe to transition directly from TCH to the paging (orIDLE) mode.

In accordance with certain aspects, direct traffic session to pagingmode transition may involve the mobile device 115 storing networkparameters prior to the call or during call setup. Exemplary before-callnetwork parameters may include a System Identification/NetworkIdentification (SID/NID) identifying which network the mobile device 115is operating on, a band class (e.g., 800 MHz, 1,900 MHz, etc.), afrequency, and/or a pilot pseudo-noise (PN) offset sequence. Othernetwork parameters may optionally include an assigned frequency receivedfrom the network in a Channel Assignment Message (CAM) or an ExtendedChannel Assignment Message (ECAM). The before-call network parametersstored prior to the call or during the call setup process may, incertain examples, be referred to as a first set of network parameters.

Other aspects may provide for the mobile device 115 to store networkparameters while in the traffic session and communicating on the TCH.These in-call network parameters may be received and/or stored as a partof the traffic session or as part of the traffic session terminationprocess (e.g., as the mobile device 115 releases the call). Thesenetwork parameters may also include a SID/NID, a band class, afrequency, and pilot PN offset sequences associated with the networkwhile in the call. These in-traffic network parameters may, in certainexamples, be referred to as a second set of network parameters. Thein-call network parameters may be different than the before-call networkparameters for various reasons. For example, situations that may changenetwork parameters include intra- or inter-network handoff, handoff to adifferent active set, and/or changes to frequency or band class due tonetwork loading or changing signal propagation characteristics. In thesesituations, the mobile device 115 may determine that the traditionalre-synchronization process (e.g., pilot signal detection and acquisitionand SYNC message reception and decoding) is required to correctlymonitor the PCH after a traffic session.

In other embodiments, the system 100 is configured to avoid networkre-synchronization procedures for stationary M2M devices. The describedtechniques may be used, for example, by a stationary M2M device 120 toconfigure the device 120 to receive paging messaging upon termination ofa traffic session without re-synchronization or acquisition of paginginformation. Before initiation of the traffic session, the M2M device120 may store paging information associated with, as one example, basestation 105-b. The paging information may include information associatedwith the PCH of the base station 105-b and which permits devices (e.g.,devices 115 and/or 120) to receive paging messages from base station105-b over the PCH. The M2M device 120 may enter into a traffic sessionwith base station 105-b to exchange information or data via the TCHassociated with a base station 105-b. When the traffic session isterminated, the M2M device 120 may be configured to receive pagingmessaging from the base station 105-b according to the stored paginginformation.

According to certain aspects, the M2M device 120 may receive and store,before the traffic session, system access information associated withbase station 105-b. Upon termination of the traffic session, the M2Mdevice 120 may determine whether the stored system access informationhas expired. For example, the stored system access information may beconsidered current if an associated overhead timer has not completed itscycle. If the overhead timer has completed the cycle, the M2M device 120may validate the stored system access information.

The stored system access information may be validated based on comparinga configuration sequence number associated with the stored system accessinformation with a current configuration sequence number. The currentconfiguration sequence number may be transmitted by base station 105-bin one or more access configuration messages. For example, the M2Mdevice 120 may receive one or more access configuration messagesincluding the current configuration sequence number and compare thecurrent configuration sequence number with the configuration sequencenumber of the stored system access information. If the comparedconfiguration sequence numbers match, the M2M device 120 may determinethat the stored system access information is valid and, therefore, doesnot need to be updated. As such, the M2M device 120 may disablereception of one or more subsequent access configuration messages.

FIG. 2 illustrates a wireless communications network 200 configured forfast traffic session to paging mode transition in accordance withvarious embodiments. Wireless communications network 200 may illustrate,for example, aspects of wireless communications network 100. Wirelesscommunications network 200 may include a mobile device 115-a, a basestation 105-d, a base station 105-e, a base station 105-f, and a basestation 105-g. Base stations 105-d, 105-e, 105-f, and 105-g may beconnected via backhaul links 232 to core network 140-a (only two of thebackhaul links 232 being shown for clarity). The base stations 105-d,105-e, 105-f, and 105-g may be connected with each other via backhaullinks 234 (only three of the backhaul links 234 being shown forclarity).

In FIG. 2, mobile device 115-a may be positioned at a location whereinit may receive pilot signals 235-d, 235-e, 235-f, and 235-g from basestations 105-d, 105-e, 105-f, and 105-g, respectively. The mobile device115-a may determine a strongest pilot signal and communicate with thebase station 105 associated with the strongest pilot signal forregistration on the network. For example, the mobile device 115-a maydetermine that pilot signal 235-e is the strongest pilot signal andregister with the base station 105-e.

Once registered, mobile device 115-a may receive various networkparameters via the PCH from base station 105-e. For example, the mobiledevice 115-a may receive a System Parameter Message (SPM), a PCH ActiveSet PN message, and/or an ECAM message on the PCH from the base station105-e. The SPM may include the SID/NID, band class, and frequencycomponents of the network parameters. The PCH Active Set PN message mayinclude an Active Set, a Candidate Set, a Neighbor Set, and a RemainingSet. The Active Set may include base stations having the strongest pilotsignals. The Candidate Set may include base stations with pilots strongenough for communication, but not listed in the Active Set. The NeighborSet may include base stations that are not in the Active Set orCandidate Set, but that are likely candidates for handoff. The RemainingSet may include other base stations in the network which are not inanother set. In the example shown in FIG. 2, the Active Set of basestations for the mobile device 115-a may be base stations 105-d, 105-e,and 105-g, whereas base station 105-f may be listed in the CandidateSet. The mobile device 115-a may store some, or all of the before-callnetwork parameters (e.g., the SID/NID, band class, frequency, etc).

During a traffic session, the mobile device 115-a may communicate via aTCH with the base stations defined in its Active Set (e.g., via links125-d, 125-e, and/or 125-g with base stations 105-d, 105-e, and 105-g,respectively). The mobile device 115-a may receive and store in-callnetwork parameters associated with the TCH from these base stationswhile in the traffic session. For example, the mobile device 115-a mayreceive and store network parameters associated with the SID/NID, theband class, the frequency, and the Active Set PN.

Various network parameters may change during the traffic session. Forinstance, the mobile device 115-a may move to a new position wherein itis closer to base station 105-f such that pilot 235-f becomes strongerthan one of pilots 235-d, 235-e, and/or 235-g. As such, the core network140-a may change the Active Set assigned to the mobile device 115-a.Similarly, other base stations may be added or dropped from the ActiveSet assigned to the mobile device 115-a during the traffic session orthe mobile device 115-a may be handed off to a different Active Set.Additionally, the Active Set may modify various parameters used forcommunicating with mobile device 115-a due to network loading or otherfactors. As the Active set changes and/or the mobile device is handedoff to base stations outside the initial Active Set, the band classand/or frequency for the mobile device 115-a may change. As such, thein-call network parameters may be different from the before-call networkparameters stored by the mobile device 115-a.

As one example of changing network parameters, any of base stations105-d, 105-e, 105-f, and/or 105-g may have the same or different networkparameters. For example, the base stations 105-e and 105-f may operateon different SID/NID, band class, frequency, etc. In that situation, themobile device 115-a may compare the before-call network parameters(i.e., network parameters associated with base station 105-e before thecall and while monitoring the PCH) with the in-call network parameters(i.e., network parameters associated with base station 105-f during thetraffic session) and determine that it is not safe to transitiondirectly from the TCH to the paging mode where the PCH of base station105-f is monitored. In that instance, traditional re-synchronizationprocedures may be followed. In accordance with another example, thenetwork parameters of base station 105-e and base station 105-f may bethe same. In that situation, the mobile device 115-a may compare thefirst and second set of network parameters and determine that direct TCHto paging mode transition is safe. In that instance, the mobile device115-a may transition directly from the TCH to the paging mode.

Wireless communications network 200 may also include stationary M2Mdevice 120-a. M2M device 120-a may be located such that pilot 235-f isthe strongest received pilot and, as a result, M2M device 120-a mayregister with base station 105-f. While registered with base station105-f, the M2M device 120-a may generally be in a sleep state or pagingmode where the M2M device 120-a is in a low-power mode and enablesreception of paging information based on a slotted paging cycle. To sendor receive information, the M2M device 120-a may enter into a trafficsession with base station 105-f, and then transition back to the sleepstate once the traffic session is complete. According to certainaspects, the M2M device 120-a may store, before the traffic session,paging information associated with the base station 105-f and thentransition directly from the traffic session to the paging mode based onthe stored paging information when the traffic session is complete.Therefore, the stationary M2M device 120-a may avoid networkre-synchronization procedures typically associated with transitioningfrom the traffic session to a sleep state. As such, the M2M device 120-amay return to the sleep state more quickly and, for example, conservepower.

Various aspects may also provide for the M2M device 120-a to storesystem access information associated with base station 105-E The systemaccess information may include information indicative of various networkparameters (e.g., SID/NID, band class, Active Set PN offset sequence),and/or information related to configuration of access channels (e.g.,preamble size, maximum size, stabilization parameters, etc.) associatedwith the base station 105-E System access information may be transmittedby base stations 105 in a number (e.g., typically seven or eight) accessconfiguration messages that each include portions of the system accessinformation. Collectively, the information in the access configurationmessages may be used by the M2M device 120-a for access procedures toinitiate communication with base station 105-E The access configurationmessages may include a configuration sequence number associated with aset of network parameters. As one example, the M2M device 120-a mayutilize a look-up table to determine the applicable network parametersassociated with the base station 105-f based on the receivedconfiguration sequence numbers.

The M2M device 120-a may store the system access information andassociate the stored system access information with an overhead timer.The stored system access information may be considered current for theduration of the overhead timer cycle and considered expired once thetimer has completed its cycle. In accordance with certain aspects, theM2M device 120-a may be configured to, after the traffic session hasended, determine if the stored system access information has expired. Ifcurrent, the M2M device 120-a may be configured to disable reception ofone or more access configuration messages. If expired (e.g., theoverhead timer has completed its cycle), the M2M device 120-a mayvalidate and, if necessary, update the stored system access information.The M2M device 120-a may validate the stored system access informationby comparing the configuration sequence number of the stored systemaccess information with a current configuration sequence number.

FIG. 3 is a diagram illustrating a communication flow 300 for directtraffic session to paging mode transition in accordance with variousembodiments. Communication flow 300 may be used, for example, by themobile devices 115 of FIGS. 1 and/or 2 for direct traffic session topaging mode transitions.

At 305, the mobile device 115-b is in a paging mode where it monitorsthe PCH from the base station 105-h (e.g., a SLEEP or IDLE state wherethe mobile device 115-b monitors the paging channel for paging and/oroverhead information associated with the base station 105-h). The mobiledevice 115-b may monitor the PCH according to paging informationassociated with the base station 105-h (e.g., a paging channel rate, apaging slot cycle, etc.). The mobile device 115-b may store before-callPCH network parameters while in the paging mode at 310. The mobiledevice 115-b may receive the before-call network parameters over the PCHwhile in the paging mode. At 315, a traffic session is initiated betweenthe mobile device 115-b and the base station 105-h. The traffic sessionmay be initiated by the mobile device 115-b or by the base station105-h. As a part of the call setup procedure for starting the trafficsession, the mobile device 115-b may, alternatively, receive and storethe before-call network parameters.

At 320, the mobile device 115-b and the base station 105-h exchangevoice and/or data information, as determined by the traffic session.While exchanging voice and/or data information in the traffic session at320, the mobile device 115-b may receive network parameters related tothe traffic session based on changes to the communication links of themobile device 115-b (e.g., the Active Set may change, handover mayoccur, etc). The received in-call network parameters associated with theTCH during the traffic session are stored at 325. The traffic sessionends at 330, where the mobile device 115-b and the base station 105-hcomplete a call-release procedure. Additionally or alternatively, themobile device 115-b may receive and store the in-call network parametersas a part of the call-release procedure.

At block 335, the mobile device 115-b may determine whether or not it issafe for a direct transition from the traffic session to a paging mode.The determination may be based on comparing the before- and in-callnetwork parameters stored at 310 and 325, respectively. For example, ifcertain before- and in-call network parameters substantially correspond,the mobile device 115-b may determine that it is safe for a directtraffic session to paging mode transition. The before- and in-callnetwork parameters may be compared in a hierarchical flow, as will bediscussed in more detail below.

Once it has been determined safe at 335, paging channel informationbased on the stored network parameters may be used at 340 for directtransition from the traffic session back to the paging mode at 345 wherethe PCH may be immediately monitored, rather than completing thetraditional re-synchronization procedure. In embodiments, the mobiledevice 115-b performs the direct transition to the paging mode withoutnetwork assistance. For example, the mobile device 115-b may determinethe paging channel information (synchronization information, pagingchannel rate, paging slot cycle, etc.) for monitoring the paging channelbased on parameters received prior to the traffic session and in thetraffic session without receiving a message related specifically toupdating the paging channel information for direct transition.

FIG. 4 is a diagram illustrating another exemplary communication flow400 for direct traffic session to paging mode transition in accordancewith various embodiments. Communication flow 400 may be used, forexample, by the mobile devices 115 of FIGS. 1 and/or 2 for directtraffic session to paging mode transitions.

At 405 the mobile device 115-c is registered or “camped” on the basestation 105-i and in a paging mode where it monitors the PCH from thebase station 105-i (e.g., in a SLEEP or IDLE state where the mobiledevice 115-c monitors the paging channel to receive paging and/oroverhead information associated with the base station 105-i). The mobiledevice 115-c may monitor the PCH according to paging informationassociated with the base station 105-i (e.g., a paging channel rate, apaging slot cycle, etc.). The mobile device 115-c may store thesebefore-call PCH network parameters while in the paging mode at 410. At415, a traffic session is initiated between the mobile device 115-c andthe base station 105-i. The traffic session may be initiated by themobile device 115-c or by the base station 105-i. As a part of the callsetup procedure for starting the traffic session, the mobile device115-c may, alternatively, receive and store the before-call networkparameters. The before-call network parameters may include a SID/NID, aband class, a frequency channel, or a pilot PN sequence associated withthe base station 105-i.

At 420, the mobile device 115-c and the base station 105-i exchangevoice and/or data information during the traffic session. Whileexchanging voice and/or data information in the traffic session 420, themobile device 115-c may receive and store in-call network parametersrelated to the traffic session based on communication links of the basestation 105-i. The in-call network parameters may include a SID/NID, aband class, a frequency channel, and/or a pilot PN sequence associatedwith the base station 105-i. At 425, the mobile device 115-c is handedover from the base station 105-i to the base station 105-j. Asdiscussed, a variety of situations may necessitate the handover. Oncethe handover process is complete, the mobile device 115-c is registeredon the base station 105-j such that base station 105-j continues thetraffic session with the mobile device 115-c at 430. As a part of thehandover process or once the mobile device 115-c is registered with thebase station 105-j and in the traffic session 430, the mobile device115-c receives and stores (e.g., updates) the in-call network parametersat 435 to reflect the network parameters associated with the basestation 105-j. That is, the mobile device 115-c may replace the in-callnetwork parameters received and stored while in traffic session 420 withbase station 105-i with the new in-call network parameters associatedwith base station 105-j. The mobile device 115-c may receive the in-callnetwork parameters associated with the base station 105-j over a TCH ofthe base station 105-j. The traffic session ends at 440, where themobile device 115-c and the base station 105-j complete a call releaseprocedure. Additionally, or alternatively, the mobile device 115-c mayreceive and store the in-call network parameters as a part of the callrelease procedure.

At 445, the mobile device 115-c may determine whether or not it is safefor a direct transition from the traffic session to a paging mode. Thedetermination may be based on comparing the before- and in-call networkparameters stored at 410 and 435, respectively. For example, if certainbefore- and in-call network parameters substantially correspond, themobile device 115-c may determine that it is safe for a direct trafficsession to paging mode transition. The before- and in-call networkparameters may be compared in a hierarchical flow as described in moredetail below.

FIG. 5 is a process diagram illustrating an exemplary process 500 for adirect transition from a traffic session to a paging mode, in accordancewith aspects of the present disclosure. The process 500 may implement,for example, aspects of wireless communications networks 100 and/or 200,as well as the communication flows 300 and/or 400. At 505, the process500 starts with a mobile device in a paging mode. For instance, any ofthe mobile devices 115 may be registered with a base station and in apaging mode where the device monitors the PCH according to paginginformation associated with the base station. Before-call networkparameters may be received over the PCH and/or stored while in thepaging mode at 505. At 510, the mobile device determines whether atraffic session should be initiated is made. The traffic session may beinitiated by the mobile device or by the base station. If no trafficsession is initiated, the process loops back to the paging mode 505where the mobile device continues to monitor the PCH for paging and/oroverhead information. If a traffic session is initiated, the processmoves to 515 where the mobile device and base station enter into thetraffic session. During the traffic session at 515, voice and/or datainformation is exchanged, depending on the nature of the trafficsession. The voice and/or data information may be exchanged via a TCHduring the traffic session.

In-call network parameters may be received and/or stored during thetraffic session 515. The in-call network parameters may relate tocommunication links associated with the traffic session. A determinationas to whether the traffic session is complete is made by the mobiledevice at 520. If the traffic session is not complete, the process 500loops back to 515 where the mobile device and base station may continuethe traffic session 515. The in-call network parameters continue to bereceived and/or stored while in the traffic session. As such, changes inthe communication links associated with the traffic session arereflected in the stored in-call network parameters (e.g., changesrelating to handoff, varying network loads, etc.).

If the traffic session is complete, the process 500 moves to 525 wherethe mobile device determines whether or not it is safe for a directtransition from the traffic session to the paging mode. Thedetermination may be based on comparing the before- and in-call networkparameters. For example, if certain before- and in-call networkparameters substantially correspond, the mobile device may determinethat it is safe for a direct transition from the traffic session to thepaging mode. The before- and in-call network parameters may be comparedin a hierarchical flow. If the mobile device determines that it is safefor a direct traffic session to paging mode transition, the mobiledevice transitions directly to the paging mode at 530 where the PCH maybe immediately monitored. If the mobile device determines that it is notsafe for a direct traffic session to paging mode transition, the process500 moves to 535 where the mobile device completes the traditionalre-synchronization procedure of pilot acquisition and sync decoding.

FIG. 6 is a process diagram illustrating an exemplary process 600 for adirect transition from a traffic session to paging mode, in accordancewith aspects of the present disclosure. More particularly, the process600 illustrated in FIG. 6 shows an exemplary hierarchical flow fordetermining whether it is safe to transition directly from the trafficsession to the paging mode. The process 600 may implement, for example,aspects of wireless communications networks 100 or 200, thecommunication flows 300 or 400, as well as aspects of the process 500.The process 600 begins at 605 where a traffic session between a mobiledevice and a base station has ended. As discussed above, before- andin-call network parameters have been received over the PCH and TCH,respectively, and subsequently stored by the mobile device. The before-and in-call network parameters may include, for example, a SID/NID, aband class, a frequency channel, an Active Set PN offset sequence,and/or other parameters.

Once the traffic session has ended at 605, the process 600 moves to 610where the mobile device may compare the SID/NID associated with thebefore-call network parameters with the SID/NID associated with thein-call network parameters. If the SID/NID parameters do not match, thisindicates that the mobile device has switched to a different networkduring the traffic session and it is not safe to transition directlyfrom the traffic session to the paging mode. In this situation, theprocess 600 moves to 655 where the mobile device completes thetraditional pilot acquisition and SYNC message decodingre-synchronization procedure.

If the SID/NID matches, then the process 600 moves to 615 where themobile device compares the band class associated with the before-callnetwork parameters to the band class associated with the in-call networkparameters. If these network parameters do not match, the mobile devicemay check to see if the in-traffic band class is listed in a frequencychannel list at 625. If the band class network parameters match, themobile device may check to see if the frequency associated with thebefore-call network parameters matches the frequency associated with thein-call network parameters at 620. Similarly, if the frequency networkparameters do not match, the mobile device may again check to see if thein-traffic frequency is listed in the frequency channel list at 625. If,at 615 and/or 620, either the band class or the frequency have changedand are not listed in the frequency channel list at 625, the mobiledevice determines that it is not safe to transition directly from thetraffic session to the paging mode. In this situation, the process 600moves to 655 where the mobile device completes the pilot acquisition andSYNC message decoding re-synchronization procedure.

If the in-call band class and frequency are listed in the frequencychannel list, the mobile device may determine that it is safe for adirect traffic session to paging mode transition. In embodiments, whenthe band class and/or frequency has changed (but the in-call band classand/or in-call frequency are in the channel list), the mobile device maytransition directly from the traffic session to the paging mode usingblind PCH decoding at 645. Blind PCH decoding refers to, for example,the mobile device attempting to decode traffic on the PCH using a lastknown good decoding scheme and/or a predetermined series of pagingchannel rates.

If the band class and frequency network parameters match at 615 and 620,the process 600 moves to 630 where the mobile device compares the ActiveSet PN offset sequence network parameters. If these network parametersmatch, then the mobile device may determine at 635 that it is safe totransition directly from the traffic session to the paging mode. If theActive Set PN offset sequences do not match, the mobile devicedetermines that it is safe to transition to the paging mode using theblind decoding scheme at 645, as discussed above.

In accordance with even further aspects, the mobile device may utilize atimer (e.g., a transition timer) to govern a reasonable amount of timeto acquire the paging channel based on stored paging channelinformation. The timer may be initiated as a part of the calltermination process and, once expired, automatically trigger the mobiledevice to revert to the standard re-synchronization process at 640. Forexample, once the mobile device transitions to the paging mode at 635,the mobile device may determine if it is able to correctly synchronizeand decode to the PCH before the timer expires. If, at 640, the timerhas expired before the mobile device correctly synchronizes and/ordecodes the PCH, the process 600 moves to 650 where the mobile devicecompletes the pilot acquisition and sync message decodingre-synchronization procedure. If the mobile device correctlysynchronizes and decodes the PCH before the expiration of the timer, theprocess 600 ends at 655.

FIG. 7 is a block diagram 700 of a device 705 for a direct trafficsession to paging mode transition in accordance with variousembodiments. The device 705 may implement aspects and/or components ofthe mobile devices 115 of FIGS. 1-4 as well as implementing aspects offlows 300 and/or 400 and/or processes 500 and/or 600. The device 705 maybe configured to safely transition directly from a traffic session to apaging mode upon completion of the traffic session. The device 705 maybe a processor.

Device 705 includes a receiver 710, a network parameters module 715, adirect transition evaluation module 720, a mode transition module 725,and a transmitter 730, which each may be in communication, directly orindirectly, with each other. The receiver 710 may receive networkparameters from a base station 105 (e.g., via the PCH) while device 705is in a paging mode or as part of a call setup procedure. The networkparameters module 715 is configured to store these before-call networkparameters. A traffic session may be initiated between the base station105 and the device 705. While in the traffic session, the receiver 710may receive various in-call network parameters (e.g., via a TCH). Thein-call network parameters may be received from one or more basestations of an active set of base stations that may vary throughout thetraffic session. The network parameters module 715 may store thesein-call network parameters. Exemplary before- and in-call networkparameters include, but are not limited to, a SID/NID, band class,frequency, etc. According to other aspects, the network parametersmodule 715 may further be configured to retrieve the stored networkparameters from, for example, a memory module (e.g., memory 940 ofmobile device 115-d). The network parameters module 715 may beconfigured to provide the stored network parameters to the directtransition evaluation module 720.

Upon termination of the traffic session, the direct transitionevaluation module 720 may determine whether it is safe for a directtraffic session to paging mode transition based on the storedbefore-call and in-call network parameters. The direct transitionevaluation module 720 may determine that it is safe for direct trafficsession to paging mode transition without assistance from the network,e.g., without requiring the network to determine, package, and/ortransmit additional paging channel information to the device 705.According to certain aspects, the determination of safe transition ismade based on comparing some or all of the before- and in-call networkparameters using a hierarchical flow. For example, the determination maybe made by following the hierarchical flow described above withreference to FIG. 6.

As discussed above, various situations might result in the before-callnetwork parameters being different from the in-call network parameters.As one example, the device 705 may move from the coverage area of asource base station to the coverage area of a target base station (seeFIG. 2 and its associated description). The network parametersassociated with the source base station may be the same as, or differentthan the network parameters associated with the target base station. Ininstances where at least some of the network parameters are the same,the direct transition evaluation module 720 may determine that it issafe for direct traffic session to paging mode transition. In instanceswhere some or all of the network parameters are different, the directtransition evaluation module 720 may determine that direct trafficsession to paging mode transition is not safe. In this instance, thedevice 705 may be configured to perform traditional re-synchronizationprocedures and proceed to pilot acquisition and sync message decoding.

According to certain aspects, the direct transition evaluation module720 may communicate whether it is safe to perform a direct transition tothe mode transition module 725. If it has been determined safe fordirect transition, the mode transition module 725 may be configured tochange an operating mode of the device 705 from the traffic sessionwhere the device 705 is communicating on the TCH (e.g., via receiver710, transmitter 730, etc.) to a paging mode where the device 705immediately monitors the PCH to receive paging information. If it hasbeen determined unsafe for direct transition, the mode transition module725 may be configured to change the mode of the device 705 from thetraffic session mode to a re-synchronization mode where the device 705may complete a pilot acquisition and SYNC message reception and decodingprocedure.

FIG. 8 is a block diagram 800 of another exemplary device 805 for adirect traffic session to paging mode transition in accordance withvarious embodiments. The device 805 may implement aspects and/orcomponents of the mobile devices 115 of FIGS. 1-4, the device 705 ofFIG. 7, as well as aspects of flows 300 and/or 400 and/or processes 500and/or 600. The device 805 may be a processor. The device 805 includes afirst receiver module 810, a second receiver module 815, a paginginformation module 820, a mode transition module 725-a, and atransmitter 830. These modules may be in communication, directly orindirectly, with each other. In one embodiment, functionality of thedevice 805 may be implemented as one or more components of the mobiledevice 115-d of FIG. 9 (e.g., the processor module 925, the paginginformation module 820-a, the mode transition module 725-b, etc.).

The device 805 may be configured to transition directly from a trafficsession to a paging mode. The first and second receiver modules 810 and815, respectively, may each be independently tunable to receiveinformation on different frequencies and/or channels. Prior to a trafficsession, the device 805 may be in a paging mode where the first receivermodule 810 or the second receiver 815 may monitor the PCH of a basestation 105. Upon initiation of a traffic session between the basestation 105 and the device 705, the first receiver module 810 may betuned to communicate via the TCH while the second receiver module 815may be tuned to receive paging information via the PCH, or vice-versa.As such, the device 805 may be able to communicate data and informationof the traffic session with the base station via the TCH whilecontinuing to receive paging information. The paging information module820 may receive the current paging information and/or network parametersfrom the first and/or second receiver modules 810 and 815. The paginginformation module 820 may maintain current paging informationassociated with the base station 105 while in the traffic session.

Upon termination of the traffic session, the mode transition module725-a may be configured to perform a direct transition from the trafficsession to the paging mode. The mode transition module 725-a may performthe direct transition based on paging information from the paginginformation module 820. The direct transition may avoid traditionalre-synchronization procedures such as pilot acquisition and sync messagedecoding.

FIG. 9 is a block diagram 900 of an exemplary mobile device 115-dconfigured for direct transition from a traffic session to a pagingmode. The mobile device 115-d may illustrate, for example, aspects ofmobile devices 115 of FIGS. 1-4, aspects of the devices 705 and/or 805of FIGS. 7-8, as well as aspects of the processes 500 and/or 600. Inembodiments, functionality of the devices 705 and/or 805 may beimplemented as one or more components of the mobile device 115-d (e.g.,the processor module 925, the network parameters module 715-a, thedirect transition evaluation module 720-a, the mode transition module725-b, the paging information module 820-a, etc.). The mobile device115-d may have any of various configurations, such as personal computers(e.g., laptop computers, netbook computers, tablet computers, etc.),cellular telephones, PDAs, digital video recorders (DVRs), internetappliances, gaming consoles, e-readers, etc. The mobile device 115-d mayhave an internal power supply (not shown), such as a small battery, tofacilitate mobile operation.

The mobile device 115-d includes antennas 905, a transceiver module 910,memory 940, and a processor module 925, which each may be incommunication, directly or indirectly, with each other (e.g., via one ormore buses). The transceiver module 910 is configured to communicatebi-directionally, via the antennas 905 and/or one or more wired orwireless links, with one or more networks, as described above. Forexample, the transceiver module 910 may be configured to communicatebi-directionally with a base station 105. The transceiver module 910 mayinclude a modem configured to modulate the packets and provide themodulated packets to the antennas 905 for transmission, and todemodulate packets received from the antennas 905. While the mobiledevice 115-d may include a single antenna, the mobile device 115-d willtypically include multiple antennas 905 for multiple links. Thetransceiver module may have multiple transmitters and/or receivers fortransmitting and/or receiving information over multiple channels and/orfrequencies at the same time. For example, the transceiver module 910may include receivers 810 and 815 of FIG. 8.

The memory 940 may include random access memory (RAM) and read-onlymemory (ROM). The memory 940 may store computer-readable,computer-executable software code 920 containing instructions that areconfigured to, when executed, cause the processor module 925 to performvarious functions described herein (e.g., direct traffic session topaging mode transition). Alternatively, the software 920 may not bedirectly executable by the processor module 925 but be configured tocause the computer (e.g., when compiled and executed) to performfunctions described herein. The processor module 925 may include anintelligent hardware device, e.g., a central processing unit (CPU), amicrocontroller, an application specific integrated circuit (ASIC), etc.

According to the architecture of FIG. 9, the mobile device 115-d mayfurther include a communications management module 930, a networkparameters module 715-a, a direct transition evaluation module 720-a, amode transition module 725-b, and/or a paging information module 820-a.By way of example, these modules may be components of the mobile device115-d in communication with some or all of the other components of themobile device 115-d via a bus. Alternatively, functionality of thesemodules may be implemented as a component of the transceiver module 910,as a computer program product, and/or as one or more controller elementsof the processor module 925. The communications management module 930may manage communications with base station 105 and/or other mobiledevices.

The mode transition module 725-b may control the current device state.In some embodiments, the mode transition module 725-b may includehardware, code, instructions, etc., configured to control transitionbetween an active state where the device 115-d is in a traffic sessionand a paging mode. The mode transition module 725-b may be configured tosafely transition the mobile device 115-d directly from the trafficsession to the paging mode upon completion of a traffic session. Themode transition module 725-b may implement the functionality of the modetransition modules 725 of devices 705 and/or 805 of FIG. 7 and/or FIG.8.

In some embodiments, the mobile device 115-d includes network parametersmodule 715-a and direct transition evaluation module 720-a. Networkparameters module 715-a may receive and store network parameters. Forexample, the network parameters module 715-a may receive variousbefore-call network parameters via the PCH from a base station 105 whilein the paging mode or as a part of a call setup procedure. The networkparameters module 715-a may further, when in a traffic session, receiveand store in-call network parameters associated with the TCH. While inthe traffic session, network parameters module 715-a may receive in-callnetwork parameters from several base stations 105 that may be part of anactive set of base stations that may vary during the traffic session.Additionally or alternatively, network parameters module 715-a may storein-call network parameters as a part of a call release procedure.Exemplary before- and in-call network parameters include, but are notlimited to, a SID/NID, band class, frequency, etc. When the trafficsession ends, the direct transition evaluation module 720-a maydetermine whether it is safe for direct traffic session to paging modetransition based on the stored network parameters. The direct transitionevaluation module 720-a may determine that it is safe for trafficsession to paging mode transition without assistance from the network,e.g., without requiring the network to determine, package, and transmitadditional paging channel information to the mobile device 115-d.According to certain aspects, the determination of safe transition ismade based on comparing some or all of the before- and in-call networkparameters using a hierarchical flow. For example, the determination maybe made by following the hierarchical flow described above withreference to FIG. 6.

In some embodiments, the mobile device 115-d includes paging informationmodule 820-a. The paging information module 820-a may be configured toreceive current paging information and/or network parameters from onereceiver of transceiver 910 while mobile device 115-d communicates in atraffic session using a second receiver of transceiver 910. The paginginformation module 820-a may maintain current paging informationassociated with a base station 105 while in the traffic session. Upontermination of the traffic session, the mode transition module 725-b maybe configured to perform a direct transition from the traffic session tothe paging mode. The mode transition module 725-b may perform the directtransition based on paging information from the paging informationmodule 820-a. The direct transition may avoid traditionalre-synchronization procedures such as pilot acquisition and sync messagedecoding

The components of the devices 705 and/or 805, and/or the mobile device115-d may, individually or collectively, be implemented with one or moreapplication-specific integrated circuits (ASICs) adapted to perform someor all of the applicable functions in hardware. Alternatively, thefunctions may be performed by one or more other processing units (orcores), on one or more integrated circuits. In other embodiments, othertypes of integrated circuits may be used (e.g., Structured/PlatformASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-CustomICs), which may be programmed in any manner known in the art. Thefunctions of each unit may also be implemented, in whole or in part,with instructions embodied in a memory, formatted to be executed by oneor more general or application-specific processors. Each of the notedmodules may be a means for performing one or more functions related tooperation of the devices 705 and/or 805, and/or the mobile device 115-d.

FIG. 10 is a flowchart of a method 1000 for safely transitioning from atraffic session to a paging mode in accordance with aspects of thepresent disclosure. The method 1000 may be performed by one or more ofthe devices 705 and/or 805 of FIG. 7 and/or FIG. 8, and/or the mobiledevices 115 of FIGS. 1-4 and/or 9. Similarly, the method 1000 mayimplement aspects of the flows 300 and/or 400 and the processes 500and/or 600. In one implementation, the processor module 925 of themobile device 115-d of FIG. 9 may execute one or more sets of codes orcomputer executable instructions to control the functional elements ofthe mobile device 115-d to perform the functions described below. Atblock 1005, the method 1000 begins where a mobile device may store,before initiation of a traffic session with a wireless communicationsnetwork, before-call network parameters (also referred to as a first setof network parameters). At block 1010, the mobile device may store,during the traffic session, in-call network parameters (also referred toas a second set of network parameters). Exemplary network parameters mayinclude, but are not limited to, a SID/NID, a band class, a frequency,and an Active Set PN offset sequence.

At block 1015, the mobile device determines, upon termination of thetraffic session, synchronization information for a direct transitionfrom the traffic session to a paging mode. The synchronizationinformation may be based on the stored network parameters. According toone implementation, the before-call and in-call network parameters arecompared using a hierarchical flow. Accordingly, if certain of thebefore-call network parameters correspond to the in-call networkparameters, the mobile device may determine it is safe for a directtraffic session to paging mode transition. In some aspects, the mobiledevice may determine it is safe to transition directly to the pagingmode, upon termination of the traffic session, using a blind PCH scheme(e.g., using last known good paging information). If the synchronizationinformation indicates that it is safe for direct transition, the methodmay continue to block 1020 where the mobile device transitions directlyfrom the traffic session to the paging mode. For example, the mobiledevice may transition directly from communication over a traffic channel(TCH) for the traffic session to receiving paging information via thepaging channel (PCH) without performing pilot signal detection andacquisition and/or synchronization channel reception and decoding.

FIG. 11 is a flowchart of a method 1100 for safely transitioning from atraffic session to a paging mode in accordance with aspects of thepresent disclosure. The method 1100 may be performed by the devices 705and/or 805 of FIG. 7 and/or FIG. 8, and/or the mobile devices 115 ofFIGS. 1-4 and/or 9. Similarly, the method 1100 may implement aspects ofthe flows 300 and/or 400 and the processes 500 and/or 600. In oneimplementation, the processor module 925 of the mobile device 115-d ofFIG. 9 may execute one or more sets of codes to control the functionalelements of the mobile device 115-d to perform the functions describedbelow. At block 1105, the method 1100 begins where a mobile device maystore, before initiation of a traffic session with a wirelesscommunications network, before-call network parameters. At block 1110,the mobile device may store, during the traffic session, in-call networkparameters. At block 1115, the mobile device determines, upontermination of the traffic session, synchronization information. Thesynchronization information may be for a direct transition from thetraffic session to a paging mode and be based on the stored networkparameters.

According to some aspects, the mobile device compares, at block 1120,the before-call and in-call network parameters. Thus, the mobile devicemay determine whether the before-call network parameters associated withmonitoring a paging channel are different than the in-call networkparameters associated with communicating via the TCH. If the storednetwork parameters substantially correspond, the method 1100 may move toblock 1125 where the mobile device may transition, based on thedetermination and comparison, directly from the traffic session to thepaging mode where the PCH may be monitored for incoming paginginformation.

FIG. 12 is a flowchart of a method 1200 for safely transitioning from atraffic session to a paging mode. The method 1200 may be performed bythe devices 705 and/or 805 of FIG. 7 and/or FIG. 8, and/or the mobiledevices 115 of FIGS. 1-4 and/or 9. Similarly, the method 1200 mayimplement aspects of the flows 300 and/or 400 and the processes 500and/or 600. In one implementation, the processor module 925 of themobile device 115-d of FIG. 9 may execute one or more sets of codes tocontrol the functional elements of the mobile device 115-d to performthe functions described below. At block 1205, the method 1200 beginswhere a mobile device may receive, by a first receiver of the mobiledevice, data signaling associated with a traffic session. At block 1210,the mobile device may receive, by a second receiver of the mobiledevice, paging signaling. The paging signaling may include one or moreof pilot sequences or synchronization signaling. As such, the mobiledevice may always have the most current paging information associatedwith the PCH.

At block 1215, the mobile device may determine, upon termination of thetraffic session, synchronization information for a direct transitionfrom the traffic session to a paging mode. The synchronizationinformation may be based on the received paging signaling from thesecond receiver. At block 1220, the mobile device may transition, basedon the determination, directly from the traffic session to the pagingmode where the PCH may be immediately monitored.

Turning now to FIGS. 13-22, methods, systems, and devices configured foravoiding network re-synchronization procedures for stationary M2Mdevices are described. FIG. 13 is a diagram illustrating an exemplarycommunication flow 1300 for avoiding network re-synchronizationprocedures in stationary M2M devices. In communication flow 1300, theM2M device 120-b may be any of the M2M devices 120 of FIGS. 1-2. At1305, the M2M device 120-b is in a sleep state where it monitors the PCHassociated with base station 105-k to receive paging and/or overheadinformation. At 1310, the M2M device 120-b stores the paginginformation. The paging information may be associated with the basestation 105-k (e.g., paging channel rate, a paging slot cycle, etc.). At1315, a traffic session is initiated between the M2M device 120-b andthe base station 105-k. The traffic session may be initiated by the M2Mdevice 120-b or by the base station 105-k.

At 1320, the M2M device 120-b and the base station 105-k exchangeinformation via the TCH, as determined by the traffic session. Thetraffic session ends at 1325. At 1330, the M2M device 120-b isconfigured for receiving paging messaging. The M2M device 120-b may beconfigured to receive the paging messaging based on the paginginformation stored at 1310. According to certain aspects, the M2M device120-b configures certain hardware elements to receive the pagingmessaging from the base station 105-k, e.g., configures hardwareelements to monitor and receive paging information via the PCH of basestation 105-k. At 1335, the M2M device 120-b performs direct transitionto the paging mode where the paging channel is monitored at 1345.

FIG. 14 is a diagram illustrating a communication flow 1400 between aM2M device 120-c and a base station 105-1, the M2M device 120-cconfigured for avoiding network re-synchronization procedures when atraffic session has ended. At 1405, the M2M device 120-c is in a sleepstate where it monitors the PCH associated with the base station 105-1to receive paging and/or system access (e.g., overhead) information. At1410, the M2M device 120-c stores the paging information and the systemaccess information. Exemplary paging information associated with thebase station 105-1 includes, but is not limited to, a paging channelrate, a paging slot cycle, etc. System access information includesvarious network parameters associated with communicating with basestation 105-1, e.g., network overhead information. At 1415, a trafficsession is initiated between the M2M device 120-c and the base station105-1. The traffic session may be initiated by the M2M device 120-c orby the base station 105-1.

At 1420, the M2M device 120-c and the base station 105-1 exchange dataand/or information via the TCH, as determined by the traffic session.The traffic session ends at 1425. At 1440, the M2M device 120-cdetermines if the system access information has expired. According tocertain aspects, the system access information is stored for a definedtime period. Accordingly, an overhead timer may be initiated when theM2M device 120-c first stores the system access information at 1410. TheM2M device 120-c may determine whether the system access information hasexpired by determining whether the associated overhead timer hascompleted its cycle. If the system access information has expired at1440, the method moves to 1445 and the M2M device receives one or moreaccess configuration messages from the base station 105-1 to update thestored system access information. The M2M device 120-c updates thesystem access information stored at 1410 with the system accessinformation received at 1445 and may reset the overhead timer. M2Mdevice 120-c may be configured for receiving paging messaging at 1450.The M2M device 120-c may be configured to receive the paging messagingbased on the paging information stored at 1410. According to certainaspects, the M2M device 120-c configures certain hardware elements toreceive the paging messaging from the base station 105-1, e.g.,configures hardware elements to monitor and receive paging informationvia the PCH of base station 105-1. At 1455, the M2M device 120-c mayperform a direct transition to the paging mode where the paging channelis monitored at 1460.

FIG. 15 is a diagram illustrating a process 1500 for avoiding networkre-synchronization procedures by transitioning from a traffic session toa paging mode in a stationary M2M device. The process 1500 mayimplement, for example, aspects of wireless communications system 100 or200, as well as the communication flows 1300 and 1400. At 1505, theprocess 1500 begins with a M2M device in a paging mode. The M2M devicemay be registered with a base station and monitoring the PCH of the basestation. The M2M device stores paging information and system accessinformation at block 1510. The paging information may be received viathe PCH of the base station. System access information may includeinformation indicative of the network parameters associated with a TCHof the base station. At 1515, a traffic session is initiated. Thetraffic session may be initiated by the M2M device or the base station.At 1520, the M2M device determines if the traffic session is complete.If not, the M2M device loops back to 1515 to continue the trafficsession. If the traffic session is complete, the process moves to 1525where the M2M device determines if the system access information hasexpired. In accordance with certain aspects, the system accessinformation may expire after a defined time period.

In one example, an overhead timer may be associated with the systemaccess information and initiated when the information is stored.Accordingly, the M2M device may determine if the overhead timer hascompeted its cycle at 1525 to determine if the system access informationhas expired. If the system access information has expired, the processmoves to 1535 where the M2M device validates and, if necessary, updatesthe system access information. The system access information may beupdated by receiving one or more access configuration messages from thebase station. The stored system access information may be updated toreflect the newly received system access information. If the systemaccess information has not expired, the process moves to 1530 where theM2M device transitions directly to the paging mode, thus avoidingnetwork re-synchronization procedures. The M2M device may be configuredto receive paging messaging based on the paging information stored at1510. For example, elements of the M2M device (hardware, software,firmware, etc.) may be configured to synchronize and decode the PCH froma base station based on the paging information.

FIG. 16 is a diagram illustrating a process 1600 for avoiding networkre-synchronization procedures in a stationary M2M device bytransitioning from a traffic mode to a paging mode. The process 1600 mayimplement, for example, aspects of wireless communications networks 100or 200, as well as the communication flows 1300 or 1400. At 1605, theprocess 1600 starts with the M2M device in a paging mode. The M2M devicemay be registered with a base station and monitoring the PCH of the basestation for paging information and/or system access information. The M2Mdevice stores the paging information and system access information at1610. The paging information may include various network parametersassociated with the PCH while system access information may includeinformation associated with communicating over a TCH of the basestation. At 1615, a traffic session is initiated. The traffic sessionmay be initiated by the M2M device or the base station. At 1620, the M2Mdevice determines if the traffic session is complete. If not, theprocess loops back to 1615 to continue the traffic session.

If the traffic session is complete, the process moves to 1625 where theM2M device determines if the system access information has expired. Inaccordance with certain aspects, expiration of the system accessinformation may be based on an overhead timer associated with the systemaccess information. If the system access information has expired, theprocess moves to 1635 where the M2M device may validate the systemaccess information by receiving one or more access configurationmessages. The access configuration messages may include a configurationsequence number that may be used by the M2M device (e.g., using alook-up table) to determine various network parameters associated withthe base station. At 1640, the M2M device determines if a configurationsequence number in the access configuration message matches acorresponding configuration sequence number associated with the systemaccess information stored at 1610. If the configuration sequence numbersmatch, it may indicate that the network parameters associated with thestored system access information are still valid (e.g., has notchanged). Accordingly, the process may move to 1630 where the M2M deviceavoids network re-synchronization procedures by transitioning directlyto the paging mode. If the configuration sequence numbers match (i.e.,the stored system access information is valid), the M2M device may avoidor disable reception of one ore more subsequent access configurationmessages. If, however, the configuration sequence numbers do not match,the process moves to 1645 where the M2M device receives and decodesadditional access configuration messages. The M2M device utilizesinformation in the access configuration messages to update the storedsystem access information at 1645 before moving to 1630 andtransitioning to the paging mode.

FIG. 17 is a block diagram 1700 of a device 1705 for avoiding networkre-synchronization in stationary M2M devices in accordance with variousembodiments. The device 1705 may implement aspects and/or components ofthe M2M devices 120 of FIGS. 1-2 and/or 13-14, as well as implementingaspects of flows 1300 and/or 1400 and processes 1500 and/or 1600. In oneembodiment, functionality of the stationary device 1705 may beimplemented as one or more components of the M2M device 120-d (e.g., theprocessor module 1970, the M2M paging information module 1715-b, the M2Mmode transition module 1720-b, etc.) of FIG. 19. Device 1705 includes areceiver 1710, M2M paging information module 1715, M2M mode transitionmodule 1720, and a transmitter 1725. These modules may be incommunication, directly or indirectly, with each other.

In embodiments, the device 1705 is a stationary device and configured toavoid network re-synchronization procedures by transitioning from atraffic session directly to a paging mode once the traffic session iscomplete. Before initiation of the traffic session, the receiver 1710may monitor a PCH of a base station 105. M2M paging information module1715 may store paging information associated with monitoring the PCH ofthe base station 105 (e.g., paging channel frequency, paging channelrate, paging slot cycle, etc.). The device 1705 may communicate data andinformation with the base station 105 on a traffic session (e.g., viareceiver 1710 and/or transmitter 1725). Upon termination of the trafficsession, the M2M paging information module 1715 may communicate thepaging information to the transition module 1720. The transition module1720 receives the paging information and may configure relevant hardwareelements of the device 1705 (e.g., receiver 1710 and/or transmitter1725, etc.) for a direct transition from the traffic session to thepaging mode based on the paging information. The device 1705, intransitioning directly from the traffic session to the sleep state, mayavoid traditional network re-synchronization procedures such as pilotsignal detection and decoding of synchronization signals and/orchannels.

FIG. 18 is a block diagram 1800 of another exemplary device 1805 foravoiding network re-synchronization in stationary M2M devices inaccordance with various embodiments. The device 1805 may implementaspects and/or components of the M2M devices 120 of FIGS. 1-2 and 13-14,and/or aspects of the device 1705 of FIG. 17, as well as implementingaspects of flows 1300 and/or 1400 and/or processes 1500 and/or 1600. Inone embodiment, functionality of the stationary device 1805 may beimplemented as one or more components of the M2M device 120-d (e.g., theprocessor module 1970, the M2M paging information module 1715-b, the M2Msystem access information module 1830-a, the M2M mode transition module1720-b, etc.) of FIG. 19. Device 1805 includes a receiver 1710-a, M2Mpaging information module 1715-a, M2M mode transition module 1720-a, atransmitter 1725-a, and M2M system access information module 1830. Thesemodules may be in communication, directly or indirectly, with eachother.

The M2M paging information module 1715-a is configured to receive andstore paging information for monitoring the PCH of a base station 105.For example, the M2M paging information module 1715-a may perform thefunctions of the M2M paging information module 1715 illustrated in FIG.17. The M2M system access information module 1830 is configured toreceive and store system access information before initiation of atraffic session. The system access information may include variousnetwork parameters associated with communicating with the base station105. For example, the system access information may include parametersfor accessing the network via an Access Channel (e.g., preamble size,maximum size, etc.). The M2M paging information module 1715-a maycommunicate the paging information to the M2M mode transition module1720-a. In accordance with certain aspects, the M2M mode transitionmodule 1720-a receives the paging information and, upon termination of atraffic session, may configure the relevant hardware elements of thedevice 1805 (e.g., receiver 1710-a, transmitter 1725-a, etc.) for adirect transition from the traffic session to the paging mode.

According to other aspects, the M2M system access information module1830 is configured to determine if the system access information remainsvalid or is expired before direct transition from the traffic session tothe paging mode. The M2M system access information module 1830 mayinclude an overhead timer associated with the stored system accessinformation. The stored system access information may be known to bevalid until at least expiration of the overhead timer. Upon terminationof the traffic session, the M2M system access information module 1830may determine whether the stored system access information has expired.If the stored system access information has expired, the M2M systemaccess information module 1830 may validate the stored system accessinformation by receiving one or more access configuration messages andconfirming whether a configuration sequence number of the stored systemaccess information matches a configuration sequence number associatedwith the one or more access configuration messages. If the configurationsequence numbers match (i.e., the stored system access information isvalid), the M2M system access information module 1830 may avoid ordisable reception (e.g., disable receiver 1710-a, etc.) of one ore moresubsequent access configuration messages. If the configuration sequencenumbers do not match, the M2M system access information module 1830 mayreceive and decode additional access configuration messages (e.g.,enable transmitter 1725-a) to update the stored system accessinformation.

FIG. 19 is a block diagram 1900 of a M2M device 120-d configured foravoiding network re-synchronization procedures. The M2M device 120-d mayillustrate, for example, aspects of the M2M devices 120 of FIGS. 1-2and/or 13-14, and/or aspects of the devices 1705 and/or 1805 of FIGS. 17and/or 18. The M2M device 120-d may also implement aspects of the flows1300 and/or 1400 and/or the processes 1500 and/or 1600. In embodiments,functionality of the devices 1705 and/or 1805 may be implemented as oneor more components of the M2M device 120-d (e.g., the processor module1970, the M2M paging information module 1715-b, the M2M mode transitionmodule 1720-b, the M2M system access information module 1830-a, etc.).The M2M device 120-d may have any of various configurations, such as asensor or monitor for various applications. The M2M device 120-d mayhave an internal power supply (not shown), such as a small battery, tofacilitate field operation.

The M2M device 120-d may include sensor 1915, antenna(s) 1945, atransceiver module 1950, a memory 1980, M2M paging information module1715-b, M2M mode transition module 1720-b, M2M system access informationmodule 1830-a, and a processor module 1970, which each may be incommunication, directly or indirectly, with each other (e.g., via one ormore buses). The sensor 1915 may monitor or track other devices,environmental conditions, etc., and provide information indicative ofthe gathered data. The transceiver module 1950 may be configured tocommunicate bi-directionally, via the antenna(s) 1945 and/or one or morewired or wireless links, with one or more networks, as described above.For example, the transceiver module 1950 may be configured tocommunicate bi-directionally with the base station 105 of FIG. 1.

The memory 1980 may include random access memory (RAM) and read-onlymemory (ROM). The memory 1980 may store computer-readable,computer-executable software code 1985 containing instructions that areconfigured to, when executed, cause the processor module 1970 to performvarious functions described herein (e.g., store paging information,communicate during the traffic session, transition back to the pagingmode, etc.). Alternatively, the software code 1985 may not be directlyexecutable by the processor module 1970 but be configured to cause acomputer (e.g., when compiled and executed) to perform functionsdescribed herein. The processor module 1970 may include an intelligenthardware device, e.g., a central processing unit (CPU), amicrocontroller, an application-specific integrated circuit (ASIC), etc.

The M2M device 120-d may be stationary and configured to avoid networkre-synchronization procedures by transitioning from a traffic sessiondirectly to a paging mode once the traffic session is complete. Beforeinitiation of the traffic session, the M2M paging information module1715-b may store paging information associated with a monitored PCH of abase station 105. Once the traffic session is complete, M2M modetransition module 1720-b may configure the relevant hardware elements ofthe M2M device 120-d (e.g., transceiver module 1950, etc.) for a directtransition from a traffic session to a paging mode based on paginginformation stored by the M2M paging information module 1715-b. In someembodiments, the M2M mode transition module 1720-b may include hardware,code, instructions, etc., configured to control transition between anactive state where the M2M device 120-d is in a traffic session and thepaging mode. The M2M device 120-d may, while in the paging mode, putvarious modules (e.g., sensor 1915, transceiver module 1950, etc.) in alow-power (or zero-power) state. Thus, the paging mode may correspond toa sleep or IDLE state of the M2M device 120-d. While in the paging mode,components necessary for reception of paging (e.g., transceiver 1950,etc.) may be enabled for short time periods to receive paging messaging(e.g., according to the paging slot cycle, etc.).

According to other aspects, the M2M system access information module1830-a may store system access information before transitioning to thetraffic session. The system access information may include variousnetwork parameters associated with communicating with a base station. Anoverhead timer may be associated with the system access information andmay indicate whether the system access information is current. The M2Mdevice 120-d may, upon termination of a traffic session, determinewhether the system access information has expired based on the overheadtimer. If the system access information has expired, the M2M device120-d may validate the system access information, and, if necessary,update the system access information by receiving access configurationmessages from the base station. Once the system access information isconfirmed valid (or updated), the M2M device 120-d may return to thesleep state.

The M2M device 120-d may further include a communications managementmodule 1960. The communications management module 1960 may managecommunications with base stations 105 and/or other M2M devices 120. Byway of example, the communications management module 1960, the M2Mpaging information module 1715-b, the M2M mode transition module 1720-b,and/or the M2M system access information module 1830-a may be componentsof the M2M device 120-d in communication with some or all of the othercomponents of the M2M device 120-d via a bus. Alternatively,functionality of these modules may be implemented as components of thetransceiver module 1950, as a computer program product, and/or as one ormore controller elements of the processor module 1970.

The components of the devices 1705 and/or 1805, and/or the M2M device120-d may, individually or collectively, be implemented with one or moreapplication-specific integrated circuits (ASICs) adapted to perform someor all of the applicable functions in hardware. Alternatively, thefunctions may be performed by one or more other processing units (orcores), on one or more integrated circuits. In other embodiments, othertypes of integrated circuits may be used (e.g., Structured/PlatformASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-CustomICs), which may be programmed in any manner known in the art. Thefunctions of each unit may also be implemented, in whole or in part,with instructions embodied in a memory, formatted to be executed by oneor more general or application-specific processors. Each of the notedmodules may be a means for performing one or more functions related tooperation of the devices 1705 and/or 1805, and/or the M2M device 120-d.

FIG. 20 is a flowchart of a method 2000 to transition from a trafficsession to a paging mode in a M2M device. The method 2000 may beperformed by the M2M devices 120 of FIGS. 1-2 and 13-14, and implementsaspects of the flows 1300 or 1400 and the processes 1500 and 1600. Inone implementation, the processor module 1970 of the M2M device 120-dmay execute one or more sets of codes to control the functional elementsof the device 120-d to perform the functions described below. At block2005, the method 2000 begins where a M2M device may store, beforeinitiation of a traffic session with a base station of the wirelesscommunications network, paging information associated with the basestation. The paging information may include information for monitoringthe PCH of the base station. At block 2010, the M2M device, once thetraffic session is complete, is configured for receiving pagingmessaging from the base station according to the stored paginginformation. As such, the method permits the M2M device to avoidtraditional network re-synchronization procedures and directlytransition to the sleep state or paging mode.

FIG. 21 is a method 2100 for a M2M device to transition from a trafficsession to a paging mode. The method 2100 may be performed by the M2Mdevices 120 of FIGS. 1-2 and 13-14. In embodiments, the method 2100implements aspects of the flows 1300 or 1400 and the processes 1500 and1600. In one implementation, the processor module 1970 of the M2M device120-d may execute one or more sets of codes to control the functionalelements of the device 120-d to perform the functions described below.At block 2105, the method 2000 begins where a M2M device may store,before initiation of a traffic session with a base station of thewireless communications network, paging information and system accessinformation. The paging information and system access information may beassociated with the base station. The paging information may includeinformation for monitoring the PCH of the base station. The systemaccess information may include information indicative of various networkparameters associated with the base station (e.g., network overheadparameters associated with communication with the base station).

At block 2110, the M2M device determines, once the traffic session iscomplete, whether the system access information has expired. Accordingto certain aspects, an overhead timer is initiated when the systemaccess information is stored. When the timer completes its cycle, thesystem access information may be considered to have expired (e.g., inneed of updating). If the system access information has not expired, theprocess moves to block 2115 where the M2M device is configured for adirect transition from the traffic session to a paging mode based on thestored paging information. As such, the method may permit the M2M deviceto avoid traditional network re-synchronization procedures upontermination of the traffic session.

FIG. 22 is a flowchart of a method 2200 for a M2M device to transitionfrom a traffic session to a paging mode. The method 2200 may beperformed by the M2M devices 120 of FIGS. 1-2 and 13-14. In embodiments,the method 2200 implements aspects of the flows 1300 or 1400 and theprocesses 1500 and 1600. In one implementation, the processor module1970 of the M2M device 120-d may execute one or more sets of codes tocontrol the functional elements of the device 120-d to perform thefunctions described below. At block 2205, the method 2200 begins where aM2M device may store, before initiation of a traffic session with a basestation of the wireless communications network, paging information andsystem access information. The paging information and system accessinformation may be associated with the base station. The paginginformation may include information for monitoring the PCH of the basestation. The system access information may include informationindicative of various network parameters associated with the basestation (e.g., network overhead parameters associated with communicationwith the base station).

At block 2210, the M2M device determines, once the traffic session iscomplete, whether the system access information has expired. Accordingto certain aspects, an overhead timer is initiated when the systemaccess information is stored. When the timer completes its cycle, thesystem access information may be considered to have expired (e.g., inneed of validating and, if necessary, updating). If the system accessinformation has expired, the process moves to block 2215 where the M2Mdevice begins the process of validating and, if necessary, updating thesystem access information. Validating and/or updating the system accessinformation may be based on a configuration sequence number received inone or more access configuration messages. The configuration sequencenumber may be utilized by the M2M device to determine network parametersassociated with the base station. In some aspects, the M2M deviceaccesses a look-up table utilizing the configuration sequence number todetermine the network parameters associated with the base station. Atblock 2220, the M2M device determines whether the configuration sequencenumber of a received access configuration message is the same as acorresponding configuration sequence number of the stored system accessinformation. At block 2220, the M2M device may determine whether theconfiguration sequence number received in the access configurationmessage is the same as the configuration sequence number previouslyreceived. If the configuration sequence numbers match, the system accessinformation may be considered valid and the process moves to block 2225where the M2M device is configured for receiving paging messaging fromthe base station according to the stored paging information. As such,the method permits the M2M device to avoid traditional networkre-synchronization procedures and also to avoid receiving unnecessaryoverhead messaging associated with updating the stored system accessinformation when the system access information has not changed.Therefore, the M2M device may return to the sleep mode where the PCH ismonitored more quickly and may further conserve power.

The detailed description set forth above in connection with the appendeddrawings describes exemplary embodiments and does not represent the onlyembodiments that may be implemented or that are within the scope of theclaims. The term “exemplary” used throughout this description means“serving as an example, instance, or illustration,” and not “preferred”or “advantageous over other embodiments.” The detailed descriptionincludes specific details for the purpose of providing an understandingof the described techniques. These techniques, however, may be practicedwithout these specific details. In some instances, well-known structuresand devices are shown in block diagram form in order to avoid obscuringthe concepts of the described embodiments.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope and spirit of the disclosure and appended claims. For example,due to the nature of software, functions described above may beimplemented using software executed by a processor, hardware, firmware,hardwiring, or combinations of any of these. Features implementingfunctions may also be physically located at various positions, includingbeing distributed such that portions of functions are implemented atdifferent physical locations. Also, as used herein, including in theclaims, “or” as used in a list of items prefaced by “at least one of”indicates a disjunctive list such that, for example, a list of “at leastone of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., Aand B and C).

Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage medium may be anyavailable medium that may be accessed by a general purpose or specialpurpose computer. By way of example, and not limitation,computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that may be used to carry or store desiredprogram code means in the form of instructions or data structures andthat may be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable aperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Throughout this disclosure the term “example” or“exemplary” indicates an example or instance and does not imply orrequire any preference for the noted example. Thus, the disclosure isnot to be limited to the examples and designs described herein but is tobe accorded the widest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method of wireless communication performed by astationary machine-to-machine (M2M) device, the method comprising:storing, before initiation of a traffic session with a base station of awireless communications network, paging information associated with thebase station; receiving, before initiation of the traffic session,system access information associated with the base station, the systemaccess information transmitted by the base station in a plurality ofaccess configuration messages; storing the received system accessinformation; determining, upon termination of the traffic session, thatthe stored system access information remains valid; transitioningdirectly to a sleep state based on the determining that the storedsystem access information remains valid; and configuring, upontermination of the traffic session, the M2M device for receiving pagingmessaging from the base station according to the stored paginginformation.
 2. The method of claim 1, wherein transitioning directly tothe sleep state comprises: disabling reception for one or more of theplurality of access configuration messages based on the determinationthat the stored system access information remains valid.
 3. The methodof claim 2, wherein the determining that the stored system accessinformation remains valid is based on an overhead timer associated withthe stored system access information.
 4. The method of claim 1, furthercomprising: determining, upon termination of the traffic session, thatthe stored system access information has expired; and validating thestored system access information prior to transitioning to a sleepstate.
 5. The method of claim 4, wherein validating the stored systemaccess information comprises: receiving one of the plurality of accessconfiguration messages; and comparing a configuration sequence numberassociated with the stored system access information to a configurationsequence number associated with the received one of the plurality ofaccess configuration messages.
 6. The method of claim 5, furthercomprising: disabling reception of one or more of the plurality ofaccess configuration messages based on determining that theconfiguration sequence number associated with the stored system accessinformation and the configuration sequence number associated with thereceived one of the plurality of access configuration messages are asame configuration sequence number.
 7. The method of claim 5, furthercomprising: enabling reception of the plurality of access configurationmessages based on determining that the configuration sequence numberassociated with the stored system access information is different fromthe configuration sequence number associated with the received one ofthe plurality of access configuration messages.
 8. The method of claim4, wherein the plurality of access configuration messages comprise oneor more of a system parameter message, an access parameter message, aneighbor list message, or a channel list message.
 9. The method of claim1, wherein the configuring the M2M device for receiving paging messagingfrom the base station comprises: configuring the M2M device forreceiving paging messaging from the base station without performing oneor more of pilot acquisition or synchronization signal decoding.
 10. Themethod of claim 1, wherein the stored paging information comprises apaging channel rate, and wherein the method further comprises: decodingpaging signaling transmitted by the base station utilizing the pagingchannel rate.
 11. The method of claim 1, wherein the stored paginginformation comprises a paging slot cycle, and wherein the methodfurther comprises: decoding paging signaling transmitted by the basestation utilizing the paging slot cycle.
 12. The method of claim 1,wherein the stored paging information comprises parameters for decodinga quick paging channel, and wherein the decoding comprises: decodingpaging signaling transmitted by the base station over the quick pagingchannel utilizing the stored paging information.
 13. The method of claim1, further comprising: receiving, during the traffic session, timinginformation for synchronization with the base station, whereinconfiguring the M2M device to receive paging messaging transmitted bythe base station based at least in part on the timing information.
 14. Awireless communications system configured to avoid networkre-synchronization procedures by a stationary machine-to-machine (M2M)device, the system comprising: means for storing, before initiation of atraffic session with a base station of a wireless communicationsnetwork, paging information associated with the base station; means forreceiving, before initiation of the traffic session, system accessinformation associated with the base station, the system accessinformation transmitted by the station in a plurality of accessconfiguration messages; means for storing the received system accessinformation; means for determining, upon termination of the trafficsession, that the stored system access information remains valid; meansfor transitioning directly to a sleep state based on the determiningthat the stored system access information remains valid; and means forconfiguring, upon termination of the traffic session, the M2M device forreceiving paging messaging from the base station according to the storedpaging information.
 15. The wireless communications system of claim 14,wherein the means for transitioning directly to the sleep state furthercomprises: means for disabling reception for one or more of theplurality of access configuration messages based on the determinationthat the stored system access information remains valid.
 16. Thewireless communications system of claim 14, wherein the determining thatthe stored system access information remains valid is based on anoverhead timer associated with the stored system access information. 17.The wireless communications system of claim 14, further comprising:means for determining, upon termination of the traffic session, that thestored system access information has expired; and means for validatingthe stored system access information prior to transitioning to a sleepstate.
 18. The wireless communications system of claim 17, wherein themeans for validating the stored system access information comprises:means for receiving one of the plurality of access configurationmessages; and means for comparing a configuration sequence numberassociated with the stored system access information to a configurationsequence number associated with the received one of the plurality ofaccess configuration messages.
 19. The wireless communications system ofclaim 18 further comprising: means for disabling reception of one ormore of the plurality of access configuration messages based ondetermining that the configuration sequence number associated with thestored system access information and the configuration sequence numberassociated with the received one of the plurality of accessconfiguration messages are a same configuration sequence number.
 20. Thewireless communications system of claim 18, further comprising: meansfor enabling reception of the plurality of access configuration messagesbased on determining that the configuration sequence number associatedwith the stored system access information is different from theconfiguration sequence number associated with the received one of theplurality of access configuration messages.
 21. The wirelesscommunications system of claim 17, wherein the plurality of accessconfiguration messages comprise one or more of a system parametermessage, an access parameter message, a neighbor list message, or achannel list message.
 22. The wireless communications system of claim14, wherein the means for configuring the M2M device for receivingpaging messaging from the base station further comprises: means forconfiguring the M2M device for receiving paging messaging from the basestation without performing one or more of pilot acquisition orsynchronization signal decoding.
 23. The wireless communications systemof claim 14, wherein the stored paging information comprises a pagingchannel rate, and the system further comprises: means for decodingpaging signaling transmitted by the base station utilizing the pagingchannel rate.
 24. The wireless communications system of claim 14,wherein the stored paging information comprises a paging slot cycle, andthe system further comprises: means for decoding paging signalingtransmitted by the base station utilizing the paging slot cycle.
 25. Thewireless communications system of claim 14, wherein the stored paginginformation comprises parameters for decoding a quick paging channel,and the system further comprises: means for decoding paging signalingtransmitted by the base station over the quick paging channel utilizingthe stored paging information.
 26. The wireless communications system ofclaim 14, further comprising: means for receiving, during the trafficsession, timing information for synchronization with the base station,wherein means for configuring the M2M device to receive paging messagingtransmitted by the base station is based at least in part on the timinginformation.
 27. A non-transitory computer readable medium storingcomputer executable code for wireless communication by a stationarymachine-to-machine (M2M) device, comprising: code for storing, beforeinitiation of a traffic session with a base station of a wirelesscommunications network, paging information associated with the basestation; code for receiving, before initiation of the traffic session,system access information associated with the base station, the systemaccess information transmitted by the base station in a plurality ofaccess configuration messages; code for storing the received systemaccess information; code for determining, upon termination of thetraffic session, that the stored system access information remainsvalid; and code for transitioning directly to a sleep state based on thedetermining that the stored system access information remains valid; andcode for configuring, upon termination of the traffic session, the M2Mdevice for receiving paging messaging from the base station according tothe stored paging information.
 28. The non-transitory computer readablemedium of claim 27, further comprising: code for disabling reception forone or more of the plurality of access configuration messages based onthe determination that the stored system access information remainsvalid.
 29. The non-transitory computer readable medium of claim 27,wherein determining that the stored system access information remainsvalid is based on an overhead timer associated with the stored systemaccess information.
 30. The non-transitory computer readable medium ofclaim 27, further comprising: code for determining, upon termination ofthe traffic session, that the stored system access information hasexpired; and code for validating the stored system access informationprior to transitioning to a sleep state.
 31. The non-transitory computerreadable medium of claim 30, further comprising: code for receiving oneof the plurality of access configuration messages; and code forcomparing a configuration sequence number associated with the storedsystem access information to a configuration sequence number associatedwith the received one of the plurality of access configuration messages.32. The non-transitory computer readable medium of claim 31, furthercomprising: code for disabling reception of one or more of the pluralityof access configuration messages based on determining that theconfiguration sequence number associated with the stored system accessinformation and the configuration sequence number associated with thereceived one of the plurality of access configuration messages are asame configuration sequence number.
 33. The non-transitory computerreadable medium of claim 31, further comprising: code for enablingreception of the plurality of access configuration messages based ondetermining that the configuration sequence number associated with thestored system access information is different from the configurationsequence number associated with the received one of the plurality ofaccess configuration messages.
 34. The non-transitory computer readablemedium of claim 30, wherein the plurality of access configurationmessages comprise one or more of a system parameter message, an accessparameter message, a neighbor list message, or a channel list message.35. The non-transitory computer readable medium of claim 27, furthercomprising: code for configuring the M2M device for receiving pagingmessaging from the base station without performing one or more of pilotacquisition or synchronization signal decoding.
 36. The non-transitorycomputer readable medium of claim 27, wherein the stored paginginformation comprises a paging channel rate, and wherein thenon-transitory computer readable medium further comprises: code fordecoding paging signaling transmitted by the base station utilizing thepaging channel rate.
 37. The non-transitory computer readable medium ofclaim 27, wherein the stored paging information comprises a paging slotcycle, and wherein the non-transitory computer readable medium furthercomprises: code for decoding paging signaling transmitted by the basestation utilizing the paging slot cycle.
 38. The non-transitory computerreadable medium of claim 27, wherein the stored paging informationcomprises parameters for decoding a quick paging channel, and whereinthe non-transitory computer readable medium further comprises: code fordecoding paging signaling transmitted by the base station over the quickpaging channel utilizing the stored paging information.
 39. Thenon-transitory computer readable medium of claim 27, further comprising:code for receiving, during the traffic session, timing information forsynchronization with the base station, wherein code for configuring theM2M device to receive paging messaging transmitted by the base stationis based at least in part on the timing information.
 40. A stationarymachine-to-machine (M2M) device configured to avoid networkre-synchronization, the device comprising: at least one controllerconfigured to: store, before initiation of a traffic session with a basestation of a wireless communications network, paging informationassociated with the base station; receive, before initiation of thetraffic session, system access information associated with the basestation, the system access information transmitted by the base stationin a plurality of access configuration messages; store the receivedsystem access information; determine, upon termination of the trafficsession, that the stored system access information remains valid;transition directly to a sleep state based on the determining that thestored system access information remains valid; and configure, upontermination of the traffic session, the M2M device for receiving pagingmessaging from the base station according to the stored paginginformation.
 41. The stationary M2M device of claim 40, wherein the atleast one controller is further configured to: disable reception for oneor more of the plurality of access configuration messages based on thedetermination that the stored system access information remains valid.42. The stationary M2M device of claim 40, wherein the determining thatthe stored system access information remains valid is based on anoverhead timer associated with the stored system access information. 43.The stationary M2M device of claim 40, wherein the at least onecontroller is further configured to: determine, upon termination of thetraffic session, that the stored system access information has expired;and validate the stored system access information prior to transitioningto a sleep state.
 44. The stationary M2M device of claim 43, wherein theat least one controller is further configured to: receive one of theplurality of access configuration messages; and compare a configurationsequence number associated with the stored system access information toa configuration sequence number associated with the received one of theplurality of access configuration messages.
 45. The stationary M2Mdevice of claim 44, wherein the at least one controller is furtherconfigured to: disable reception of one or more of the plurality ofaccess configuration messages based on determining that theconfiguration sequence number associated with the stored system accessinformation and the configuration sequence number associated with thereceived one of the plurality of access configuration messages are asame configuration sequence number.
 46. The stationary M2M device ofclaim 44, wherein the at least one controller is further configured to:enable reception of the plurality of access configuration messages basedon determining that the configuration sequence number associated withthe stored system access information is different from the configurationsequence number associated with the received one of the plurality ofaccess configuration messages.
 47. The stationary M2M device of claim43, wherein the plurality of access configuration messages comprise oneor more of a system parameter message, an access parameter message, aneighbor list message, or a channel list message.
 48. The stationary M2Mdevice of claim 43, wherein the at least one controller is furtherconfigured to: configure the M2M device for receiving paging messagingfrom the base station without performing one or more of pilotacquisition or synchronization signal decoding.
 49. The stationary M2Mdevice of claim 43, wherein the stored paging information comprises apaging channel rate, and wherein the at least one controller is furtherconfigured to: decode paging signaling transmitted by the base stationutilizing the paging channel rate.
 50. The stationary M2M device ofclaim 43, wherein the stored paging information comprises a paging slotcycle, and wherein the at least one controller is further configured to:decode paging signaling transmitted by the base station utilizing thepaging slot cycle.
 51. The stationary M2M device of claim 43, whereinthe stored paging information comprises parameters for decoding a quickpaging channel, and wherein the at least one controller is furtherconfigured to: decode paging signaling transmitted by the base stationover the quick paging channel utilizing the stored paging information.52. The stationary M2M device of claim 43, wherein the at least onecontroller is further configured to: receive, during the trafficsession, timing information for synchronization with the base station,wherein the controller is configured to configure the M2M device toreceive paging messaging transmitted by the base station based at leastin part on the timing information.